Skip to main content
Glama
fsans

FileMaker Data API MCP Server

by fsans

fm_config_add_connection

Add a new FileMaker database connection to the configuration using connection name, server, database, user, and password.

Instructions

Add a new predefined FileMaker database connection to the configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesConnection name (e.g., 'production', 'staging', 'dev')
userYesFileMaker username
serverYesFileMaker Server IP address or hostname (without https://)
versionNoFileMaker Data API version (default: vLatest)
databaseYesFileMaker database name
passwordYesFileMaker password
Behavior2/5

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

No annotations provided. Description does not disclose side effects (e.g., overwriting existing connection), required privileges, or connection validation behavior.

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

Conciseness4/5

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

Single, clear sentence. Could include more context without losing conciseness, but not overly verbose.

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

Completeness2/5

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

Critical operation with 6 parameters and no output schema; description lacks information on duplicate handling, validation, or what 'configuration' entails. Incomplete for effective use.

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

Parameters3/5

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

Schema covers 100% of parameters with descriptions. Description adds no additional meaning beyond the schema (e.g., uniqueness of name, default version).

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?

Clearly states action 'add' and resource 'predefined FileMaker database connection to configuration'. Differentiates from sibling tools like remove, list, get, set_default, and fm_connect.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., fm_connect or fm_set_connection) or any prerequisites or constraints.

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/fsans/FileMaker-Server-DAPI-MCP'

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