Skip to main content
Glama

breadboardhub circuits

Get a design

get_design
Read-only

Gets one public design by its owner's username and the design's slug, as shown in search results and in breadboardhub design links.

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": {
      "username": "<username>",
      "slug": "<slug>"
    },
    "name": "get_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds one genuinely new behavior: only PUBLIC designs are retrievable, implying private or draft designs will not resolve. There is no output schema, so return values are unaddressed.

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

Conciseness4/5

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

A single front-loaded sentence with the verb and scope first and the identifier provenance second. Nothing is redundant, though the trailing clause about breadboardhub links is slightly wordy.

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 two-parameter read-only lookup with a covered safety profile, the definition supplies enough to call it correctly: what is fetched, the key pair, and where to obtain the key values. Only failure semantics (not found, private design) remain unstated.

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 0%, so the description carries the full burden and mostly does: it identifies username as the owner's username and slug as the design's slug, and points to search results and design links as the source of valid values. It does not state format constraints such as case sensitivity or whether the username includes a leading prefix.

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?

States a specific verb and resource ('Gets one public design') and scopes it to a single record keyed by owner username and slug, which contrasts implicitly with the plural search_designs sibling. It stops short of naming that sibling, so the differentiation is inferred rather than stated.

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?

The clause 'as shown in search results and in breadboardhub design links' tells the agent where the two identifiers come from, which is a practical usage hint. It does not say when to prefer this over search_designs or what to do if the lookup fails, so the guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources