Skip to main content
Glama
Sign In

Schematik

by io.schematik
OverviewDiscussionsAdmin

Search parts

search_parts
Read-onlyIdempotent

Search Schematik's public electronics parts catalogue (boards, sensors, displays, modules) by name, brand, part number or use. Returns a JSON list of parts, best matches first; pass a result's slug to get_part for its pinout and price.

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_parts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many parts to return at most. Fewer come back when fewer parts match.
queryYesWords to match, e.g. a part name, brand, part number or use such as 'BME280' or 'oled display'. Parts matching any word are returned, best matches first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Most results to return."New value: +"How many parts to return at most. Fewer come back when fewer parts match."
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Most results to return."
    • addedInput schema / properties / query / description
      Added value: +"Words to match, e.g. a part name, brand, part number or use such as 'BME280' or 'oled display'. Parts matching any word are returned, best matches first."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds that results come back as a JSON list ordered best-match-first and that each result carries a slug usable downstream, but says nothing about empty result sets, matching tolerance or rate limits.

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: the identity/scope sentence comes first, then the return shape and the handoff to get_part. No filler, no repetition of annotation data.

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 no output schema, the description usefully compensates by describing the return type, ordering and the slug field needed to chain into get_part. Complete enough to call correctly; only edge-case behavior (no matches, truncation by limit) is left implicit.

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 description coverage is 100%, so both query and limit semantics (any-word matching, max 20, default 10) are already documented in structured form. The description mainly restates the searchable field kinds and adds only the 'slug' output handle as new meaning.

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?

States a specific verb and resource ('Search Schematik's public electronics parts catalogue') and enumerates the resource types and matchable fields (name, brand, part number, use). A 'parts catalogue' search is clearly distinct from the sibling build-guide tools, and the follow-up tool get_part is named.

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?

Gives the trigger conditions (search by name, brand, part number or use) and explicitly routes the agent to get_part when pinout and price are needed, which is the main branching decision for this tool family. It stops short of stating exclusions, e.g. that this does not search build guides.

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

All Schematik toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources