Skip to main content
Glama

guide

Read-only

Retrieve CopperFlow skill documentation and topic-specific references to support PCB design tasks when the skill is not installed.

Instructions

The copperflow skill: SKILL.md, or a reference with a topic. A text already read answers a short line unless again. Call it when the skill is not installed.

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

Input Schema

NameRequiredDescriptionDefault
againNo
topicNoOne of planning, design-workflow, copper, writing-circuits, parts-library, design-rules, editable-subset, modules, or packages [words]: the footprint strings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description contributes a real behavioral detail beyond that — a deduplication/caching behavior where an already-read text yields only a short line unless 'again' is set — which is useful but phrased so opaquely that its exact trigger and effect remain ambiguous.

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

Conciseness3/5

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

It is short — three sentences — so length is not the issue. But the sentences are grammatically broken and not front-loaded: the core action and its condition ('when the skill is not installed') arrive last and buried in a subordinate clause.

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?

With no output schema, the description must explain the return value, and it only vaguely says 'a text ... answers a short line.' For a zero-required-parameter documentation tool with an undocumented boolean, an agent still lacks the information needed to decide between the full-text and short-line paths and to pick a valid topic.

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 only 50%: 'topic' is documented with an enumerated-looking list of values, while 'again' is an undescribed boolean. The description partially compensates by implying 'again' forces the full text on re-read, but it does not explain the value of the short line versus full text, nor confirm the topic strings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a set of sentence fragments: 'The copperflow skill: SKILL.md, or a reference with a topic.' It gestures at retrieving skill documentation or a topic-specific reference, but never states a clear verb or what exactly is returned, so an agent must guess whether this fetches a file, a doc, or a summary. It is close to restating the name 'guide' rather than defining the operation.

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

Usage Guidelines3/5

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

There is one explicit condition: 'Call it when the skill is not installed,' plus an implied rule that a previously-read text only returns a short line unless 'again' is passed. Neither is elaborated — nothing says how to determine whether the skill is installed, or which sibling to use instead when it is.

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