Skip to main content
Glama

Find what uses an object of the file

patchwork_uses
Read-onlyIdempotent

Reports what references or mentions an object, without changing anything, so you can check what would break before deleting or renaming it.

Instructions

Report what uses an object, without changing anything: references (certain) and mentions of its name in calculations (possible). Call it before patchwork_delete or before renaming, to see what would break. Answers 'Nothing in the file uses ...' when nothing does.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "<kind>",
      "name": "<name>"
    },
    "name": "patchwork_uses"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesKind of the object to look up.
nameYesExact name of the object. Table::Field for a field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so 'without changing anything' is mostly redundant. Beyond that, the description discloses genuinely useful behavior the annotations do not: results are split into certain references and possible name mentions, and it specifies the empty-result message ('Nothing in the file uses ...'), which tells the agent how to detect a negative answer.

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 earning its place: what is returned, when to call it, and how emptiness is reported. The core verb and the certain/possible split are front-loaded with no filler.

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?

There is no output schema, so the description has to convey return semantics, and it does so at a high level (reference results vs calculation mentions, plus the empty-case message). Minor gaps remain around result shape and whether the search is scoped to the open file, but for a two-parameter read-only lookup this is close to complete.

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 coverage is 100%, including the enum of kinds and the 'Table::Field for a field' naming convention, so the schema carries the parameter burden. The description's mention of matching 'its name in calculations' hints that the name is matched textually and can yield false positives, which adds some meaning, but it does not explain matching rules, case sensitivity, or scoping to the current file.

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 ('Report what uses an object') and immediately qualifies the two result classes it returns: certain references versus possible mentions of the name in calculations. That distinction lets an agent distinguish this lookup tool from the mutation siblings without opening the schema.

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?

Gives concrete trigger conditions: call before patchwork_delete or before renaming, framed as 'see what would break.' That is clear when-to-use guidance tied to specific sibling operations, but there is no explicit statement of when the tool is unnecessary or what to do with the result.

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