Skip to main content
Glama
SpiceMCP
by oniondas

list_templates

Lists ready-made circuit templates for filters, amplifiers, LDOs, and buck converters, with the specifications each requires. Use it when a user describes a circuit instead of providing a netlist.

Instructions

List ready-made circuits (filters, amplifier, LDO, buck) and the spec each needs. Start here when the user describes a circuit instead of giving a netlist.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the return content ('the spec each needs') for what is plainly a zero-parameter read. It omits whether the returned items are identifiers consumable by start_from_template and says nothing about ordering or completeness of the catalog.

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?

Two sentences, no filler: what it returns first, when to reach for it second. Every clause carries information an agent needs for selection.

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?

For a zero-parameter, no-output-schema listing tool, purpose and trigger condition are both covered, which is most of what an agent needs. A brief note on how the listed specs map to a subsequent start_from_template call would close the remaining gap.

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 no parameters, so there is nothing for the description to disambiguate. Baseline 4 applies since the empty object schema leaves no semantic gaps to fill.

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

Purpose4/5

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

The description gives a specific verb ('List') and resource ('ready-made circuits') and even enumerates example categories (filters, amplifier, LDO, buck), so an agent knows exactly what comes back. It stops short of naming a sibling such as start_from_template as the follow-on, so differentiation is implied rather than explicit.

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?

'Start here when the user describes a circuit instead of giving a netlist' is a clear entry condition with an implicit exclusion (netlist already provided). It does not state what to call after a template is chosen, leaving the next-step routing to be inferred.

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