Skip to main content
Glama
nietsneuah

filemaker-mcp

by nietsneuah

fm_get_schema

Retrieve the database schema from FileMaker, including field names, types, and primary keys, to build accurate queries. Optionally list all available tables or get details for a specific table.

Instructions

Get the database schema (field names and types) from FileMaker.

Use this to discover exact field names, their types, and primary keys before constructing queries. Essential for building accurate filter and select expressions.

IMPORTANT: Always call this with a specific table name before querying that table for the first time — many field names contain spaces.

Schema is cached in memory for the session. If you need a table not in the standard list, just request it — the server will auto-discover it from FileMaker.

Args: table: Table name to get fields for (e.g., "Customers", "Orders"). Leave empty to list all available tables. You can request any table that exists in FileMaker — not just the standard list. Unknown tables are auto-discovered. refresh: Force re-fetch from live FM server. Use when you suspect the schema has changed (e.g., new fields added in FileMaker). Default uses cached DDL (instant, no API call). show_all: Show all fields including internal/system fields. Default hides internal fields (globals, speed fields, etc.) to keep schema output concise.

Returns: Formatted listing of fields with names, types, and annotations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableNo
refreshNo
show_allNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses caching, auto-discovery of tables, and refresh behavior. No annotations exist, so description carries full burden; it covers non-destructive nature and return format but could mention any authorization requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear paragraphs, front-loaded purpose, and no wasted words. Efficiently conveys all necessary information in a digestible format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description sufficiently explains returns. It covers all 3 parameters, usage context, and caching behavior. No gaps for typical agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description thoroughly explains each parameter: table (name/empty behavior), refresh (force re-fetch), show_all (internal fields). Adds meaning like auto-discovery and caching details not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves the FileMaker database schema (field names and types). It differentiates from sibling tools by emphasizing schema discovery for query construction, and explicitly links to usage before querying tables.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance to call with a specific table before first query, mentions caching, and refresh for stale schema. Does not directly contrast with fm_list_tables, but the context is clear enough for proper use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nietsneuah/filemaker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server