Skip to main content
Glama
nietsneuah

filemaker-mcp

by nietsneuah

fm_load_dataset

Load FileMaker records into a named dataset for fast analytics. Fetch records once, store as pandas DataFrame, then run multiple analyses without extra database round trips.

Instructions

Load FileMaker records into a named dataset for fast analytics.

Fetches records from FM and stores them as a pandas DataFrame in session memory. Load once, then run multiple analyses with fm_analyze — no additional FM round trips needed.

Auto-paginates if more than 10,000 records match. Loading a dataset with an existing name replaces it (refresh).

IMPORTANT: Call fm_get_schema(table) first to discover field names.

Args: name: Your chosen identifier for this dataset (e.g., "inv25", "customers"). table: FM table to query (see fm_list_tables for available tables). filter: OData $filter expression. Use exact field names from get_schema. Example: "ServiceDate ge 2025-01-01 and ServiceDate lt 2026-01-01" select: Comma-separated fields to fetch. Leave empty for all fields. TIP: Select only the fields you need — reduces memory and speeds loading. Example: "Technician,Region,Amount,ServiceDate"

Returns: Summary with row count, columns, and memory usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
tableYes
filterNo
selectNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses replacement behavior, auto-pagination, and in-memory storage. No annotations provided, so description carries burden; it covers key behaviors but could mention error handling.

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 sections, no fluff, every sentence adds value. Purpose is front-loaded, followed by details and examples.

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 complexity, sibling tools, and presence of output schema, the description is complete. It explains return summary, prerequisites, and examples.

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?

Schema has 0% coverage, so description must define parameters. It explains each parameter clearly: name as identifier, table as FM table, filter with OData example, select with memory-saving tip.

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 it loads FM records into a named dataset for analytics, stores as DataFrame, and distinguishes from siblings like fm_query_records and fm_analyze.

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

Usage Guidelines5/5

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

Provides explicit prerequisite (call fm_get_schema first), tips on select field, and context for auto-pagination and dataset replacement. Clear guidance on when and how to 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