Skip to main content
Glama
Sign In

Schematik

by io.schematik
OverviewDiscussionsAdmin

Get part

get_part
Read-onlyIdempotent

One part from the catalogue by slug, as JSON: name, brand, part number, description, category, an available vendor price (lowest offer in one currency, USD when available, e.g. 'from 4.5 USD'), pinout and a link to its Schematik page. Brand, part number, description, price and pinout can be null when unavailable.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe part's slug as returned by search_parts, e.g. 'bme280-i2c-sensor'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"The part's slug as returned by search_parts, e.g. 'bme280-i2c-sensor'."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description does add real context beyond them: which fields can be null and how the price is derived (lowest offer, USD preferred). It does not state what happens when a slug is not found, leaving the main failure mode undisclosed.

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?

Two sentences, both substantive: the first front-loads the action and the return shape, the second covers nullability. The field list is dense and slightly run-on but every item is useful for an agent reasoning about the response.

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 carries the return-value burden and does so well by naming the fields, the price format, and null-ability. The only meaningful gap for a one-parameter read tool is the not-found behavior.

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?

There is a single parameter with 100% schema description coverage, including an example slug, so the schema does the work. The description adds no format, casing, or normalization guidance beyond the phrase 'by slug'; baseline 3 applies.

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: 'One part from the catalogue by slug,' which contrasts cleanly with the sibling search_parts (single fetch vs. search). The enumeration of returned fields reinforces what the tool delivers, though it never explicitly frames itself against search_parts or the build-guide siblings.

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?

Usage is only implied: 'by slug' signals a lookup that requires an identifier obtained elsewhere, but the description never says to call search_parts first or when not to use this tool. The schema's slug description ('as returned by search_parts') carries that routing information instead of the description.

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