Skip to main content
Glama
Sign In
Copper

Copper

by claynicholson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Tool help

copper_help
Read-onlyIdempotent

Retrieve worked examples, operation catalogues, and argument details for Copper tools. Call before complex use or after BAD_ARGUMENT/BAD_OP errors.

Instructions

Worked examples, op catalogues and argument details for one Copper tool: the long-form help that is kept out of the tool list. Call it before your first non-trivial use of a tool, or when a call came back BAD_ARGUMENT / BAD_OP. Omit tool to list every tool with a one-line summary. Example: copper_help(tool='sch_apply')

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": "copper_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNotool name, e.g. 'pcb_route'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.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 it read-only, idempotent, and closed-world, so the safety profile is covered; the description adds real content beyond them — what the returned text contains, the enumerate-all fallback, and the error-recovery role. The remaining gap is that it does not say what happens with an unrecognized tool name or how large the returned help text is.

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?

Front-loaded purpose followed by when-to-call, the omit-parameter behavior, and a concrete example — four short sentences with no filler. The parenthetical on the first line earns its place by explaining why this exists outside the tool list.

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 one optional parameter, no output schema, and read-only annotations, the description covers what an agent needs to decide and call. The one thing left implicit is the volume/format of the returned help text, which matters for a documentation-dumping tool.

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% and the single `tool` parameter is optional, but the schema only says 'tool name, e.g. pcb_route'. The description supplies the crucial semantic the schema omits: omitting `tool` switches the tool into a catalog/listing mode, and it shows a concrete call form.

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 names a specific resource and behavior: long-form help (worked examples, op catalogues, argument details) for one named Copper tool, plus a list mode when `tool` is omitted. That scope is clearly distinct from the action siblings (sch_apply, pcb_route, etc.), which are never described as documentation lookups.

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?

It gives explicit triggers: call before a first non-trivial use of a tool, or after a call returned BAD_ARGUMENT / BAD_OP, and names the fallback (omit `tool` to list everything). An agent knows both when to reach for this tool and what the alternative call shape is.

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

Deploy Server

Other Tools