Skip to main content
Glama

breadboardhub circuits

Search circuit designs

search_designs
Read-only

Searches public circuit, firmware and schematic designs shared on breadboardhub. Returns names, types, tags, stars and 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": {
      "query": "<query>"
    },
    "name": "search_designs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to search for (2 to 100 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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, covering the safety profile. The description usefully adds what comes back (names, types, tags, stars, links) and that only public shared designs are in scope, but says nothing about result ordering, pagination, or the 10-result cap.

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 tight sentences, front-loaded with the action and scope, followed by the return shape. Every clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with annotations and no output schema, disclosing the returned fields covers most of what an agent needs. The gaps are the undocumented limit cap and absence of any note on result ordering or paging, which matter for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: query has an inline description, but limit has none beyond min/max bounds. The description adds no meaning about parameters at all — no mention of the result cap or what a larger limit does — so it fails to compensate for the undocumented parameter.

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 clear verb and resource ('Searches public circuit, firmware and schematic designs') plus the hosting scope ('shared on breadboardhub'), which distinguishes a discovery tool from siblings like get_design or design_circuit. It stops short of explicitly naming a sibling to contrast with, so it is clear but not maximally differentiated.

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

Usage Guidelines2/5

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

Nothing states when to use this versus get_design for fetching a known design, or versus design_circuit/simulate_circuit. The word 'public' hints that only shared community designs are reachable, but no when-to-use or when-not-to-use condition is stated.

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