Skip to main content
Glama

VOLT48 — 48V DC telecom power

Product family detail

get_family
Read-onlyIdempotent

Full detail of one product family by id (from search_parts): lifecycle status, models and part numbers, applications, what to send for a quotation, honest alternatives, page.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the returned content sections (including 'honest alternatives'), which matters given there is no output schema, but it says nothing about behavior on an unknown/stale id or how the 'page' field relates to pagination.

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?

A single front-loaded sentence with the primary action first and the payload contents as a compact list. No filler, no restatement of the name or title.

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 enumeration of returned sections is exactly the right compensating detail, and the id provenance closes the main workflow gap. Missing only the failure/edge behavior and where the returned 'page' data leads next (request_quote).

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% for the single id parameter, so the description must carry the meaning — and it does by identifying the id as a product-family id obtained from search_parts. It does not specify format or whether an unknown id errors versus returns empty.

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?

Names a specific verb (full detail of one product family) and the keying resource (by id), then enumerates what the record contains: lifecycle status, models/part numbers, applications, quote requirements, alternatives, page. It also distinguishes itself from search_parts by naming it as the id source.

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?

States the precondition for use — the id comes from search_parts — which implicitly makes this a follow-up drill-down rather than a discovery tool. It stops short of explicit when-not-to-use guidance or naming request_quote as the next step for the quotation data it surfaces.

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