Skip to main content
Glama

Feature Library

Get a part’s card

get_part
Read-only

The free card always (summary, role, needs, costs, public API signatures, pitfall titles, pairs-with). With a licence token that owns the part: the licensed card too, with every pitfall in full, the guide, documented signatures, the module’s files and the changelog. Read every pitfall before building with it.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe part id (an old id resolves to the renamed part).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a genuine behavioral trait: output depth is conditional on licence ownership of the part. That is the kind of context annotations cannot convey. It stops short of stating failure behavior when a licence token is absent or invalid.

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 dense sentences, front-loaded with the free tier and then the licensed tier, with no filler. The parenthetical field list is long but each item earns its place by telling the agent what to expect back.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating the free and licensed payloads. The one ambiguity is the unexplained source of the licence token, since the input schema exposes only `id`, leaving the agent to infer it comes from ambient auth.

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 coverage is 100% and the single `id` parameter already documents that old ids resolve to renamed parts, so the description correctly does not repeat it. It adds no further meaning about the identifier (format, source, where to obtain it), which is acceptable given the schema baseline.

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 concrete verb+resource and enumerates the returned payload (summary, role, needs, costs, signatures, pitfall titles, pairs-with), which is far more specific than a restated title. It does not explicitly contrast itself with siblings like get_brief or get_kit, so the agent must infer that this is the full part card rather than a slice.

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 licence-token clause implicitly tells the agent what it will receive in each auth state, and "Read every pitfall before building with it" gives a downstream usage instruction. However there is no explicit when-to-use versus alternatives (find_parts to locate a part, get_brief for a lighter view), so routing is only implied.

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