Skip to main content
Glama

VOLT48 — 48V DC telecom power

Search 48V DC telecom power by part number

search_parts
Read-onlyIdempotent

Search VOLT48's catalogue of 48V DC telecom power equipment — rectifier modules (Eltek Flatpack2/Flatpack S, Huawei R4850G2, Vertiv/Emerson NetSure, Delta ESR, Eaton APR48, ZTE ZXDU), plant controllers and 48V LiFePO4 batteries — by part number, brand or model. Returns lifecycle status, models and part numbers. No prices or lead times.

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
limitNo
queryYese.g. "R4850G2", "241115.105", "Flatpack2", "LiFePO4 100Ah"

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?

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. Beyond that, the description usefully discloses what comes back (lifecycle status, models, part numbers) and what does not (prices, lead times), though it says nothing about result caps or the meaning of the limit parameter.

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, front-loaded with the scope and catalogue contents, then the return and exclusion notes. The long brand enumeration is dense but earns its place as retrieval hints; nothing is redundant.

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?

For a simple two-parameter read tool with no output schema, the description covers the query domain and the shape of the response, which is what an agent needs to select and call it. The only gap is the undocumented limit parameter and any result-count 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?

Schema coverage is 50%: query has an example-bearing description while limit has only min/max bounds. The description partially compensates by listing acceptable query forms (part number, brand, model, plus concrete examples like R4850G2 and Flatpack2), but the limit parameter remains unexplained in both places.

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 (search) and resource (48V DC telecom power catalogue), and enumerates the equipment classes and brands covered, so an agent knows exactly what domain it queries. It also scopes out prices and lead times, which implicitly separates it from a quoting tool, but no sibling is named explicitly.

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 description tells the agent it can search by part number, brand or model and that prices/lead times are out of scope, which implies pricing belongs to another tool. However, it never states when to prefer this over get_family or get_terms, nor any prerequisite or exclusion condition.

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