Skip to main content
Glama

Show the state of the working copy

patchwork_status
Read-onlyIdempotent

Check whether a FileMaker file is open and view its working-copy version, account, and object counts. Use it to confirm the active version before making versioned edits.

Instructions

Summary of the working copy: source file, current version with its message and time, account, and counts of tables, layouts, scripts, value lists and custom functions. Use it to check that a file is open and which version you are on. For every version use patchwork_log; for object names use patchwork_list.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered; the description adds real value by disclosing the shape of the response (file, version, message, time, account, object counts), which matters since there is no output schema. It stops short of stating edge behavior such as what is returned when no file is open, which would complete the picture.

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 tight sentences: the first front-loads what is reported, the second states the use case, the third routes to alternatives. No filler, no repetition of the title, and the most important information leads.

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

Completeness4/5

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

With no parameters, no output schema, and safety fully covered by annotations, the definition supplies the missing return-value description and sibling routing, making it complete for correct invocation. The only gap is the absence of any statement about failure/empty state when no working copy is open.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to describe. The description correctly does not invent arguments and instead spends its words on scope and return content.

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 opens with a specific resource ('Summary of the working copy') and enumerates exactly what it reports: source file, current version with message and time, account, and counts of tables/layouts/scripts/value lists/custom functions. It also explicitly distinguishes itself from patchwork_log and patchwork_list, so an agent can route correctly without reading sibling schemas.

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?

Gives an explicit when-to-use ('check that a file is open and which version you are on') plus two named alternatives with their conditions: patchwork_log for every version, patchwork_list for object names. Nothing is left to inference about which tool to pick.

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