Skip to main content
Glama

List the objects of the file by kind

patchwork_list
Read-onlyIdempotent

List FileMaker object names one per line by kind, or count objects per kind when omitted. Retrieve exact table, field, script, layout, value list, theme, and custom function names before editing or inspecting with other Patchwork tools.

Instructions

List the names of the objects of one kind, one per line. Without kind, returns a count per kind instead. kind=fields needs table and returns each field as name, tab, type, with (calc) for a calculation. Use it to get exact names before patchwork_show, patchwork_uses or any edit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "patchwork_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoKind of object to list. Omit for a count per kind.
tableNoBase table name. Required with kind=fields, ignored otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description earns credit for disclosing return shape: one name per line, a count-per-kind mode, and the field format "name, tab, type, with (calc) for a calculation." That is meaningful output behavior, though there is no mention of error conditions or ordering of the listing.

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?

Three short sentences, each carrying distinct information: default behavior, parameter dependency, and workflow placement. No filler or redundancy, and the primary behavior is front-loaded.

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?

A two-parameter, read-only enumeration tool with no output schema; the description supplies the return format, the default-vs-filtered behavior, the conditional parameter rule, and where it fits relative to sibling tools. Nothing an agent needs in order to call it correctly appears to be missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining the cross-parameter dependency: table is required only with kind=fields and ignored otherwise. It also clarifies the semantics of the fields output rather than just the parameter names.

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?

States a specific verb and resource ("List the names of the objects of one kind, one per line") and immediately covers the no-argument case ("Without kind, returns a count per kind instead"). It also names the sibling tools it feeds into (patchwork_show, patchwork_uses), so an agent can place it in the workflow without opening other schemas.

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?

Explicitly says to use it "to get exact names before patchwork_show, patchwork_uses or any edit," which gives a clear triggering context. It also states the conditional rule that kind=fields needs table and that table is ignored otherwise. It stops short of an explicit when-not-to-use statement, but for a read-only lister the guidance is solid.

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