MCP tool reference

Note  Reference only This page is for informational purposes. Coding agents discover these tools and their current schemas directly from the ADT MCP server. End users and developers do not choose or invoke the tools themselves.

Note  Subject to change Tool names, inputs, and outputs can change between ADT releases. The coding agent uses the definitions published by the installed MCP server, which take precedence over this overview.

The MCP server is how an agent reaches FileMaker during a conversation. Its tools are registered by the coding agent plugin, not configured by hand. The sections below provide a brief overview of what each tool allows the agent to do.

Diagnostics

troubleshoot_setup is the first call in any setup problem. Its report is scoped to the current working directory and the open file, and it distinguishes the agent session's authorization from a shell session's. A report carrying notDiagnosed is narrowed, not passing.

Connection discovery

connectedFiles answers what the agent can see: which files the project records, and which are open in FileMaker Pro.

Table and layout metadata

table_metadata and layout_metadata answer what a table or layout contains. A generated data client and a data-access layout both depend on the latter.

Schema

get_filemaker_ddl_schema returns a DDL rendering of the whole file, for orientation before any change.

SQL queries

execute_filemaker_sql is the read path for record data. Read-only, and FileMaker's SQL dialect has its own quoting and naming rules.

Records

data_api_orchestrator is the only tool here that changes data. It acts as the connected account, through a layout, and respects that account's privileges.