Skip to main content
Glama

VOLT48 — 48V DC telecom power

Record a sourcing request

request_quote

Record a sourcing requirement with VOLT48 on behalf of a buyer (telecom operator, ISP, integrator, data-centre team): part numbers or descriptions with quantities. VOLT48 is selecting its manufacturing partners; the request is recorded and quoted once a supplying factory is confirmed. Nothing is binding and nothing is sent automatically. Only call with the buyer's consent to share their contact details.

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": {
      "buyer": "<buyer>",
      "lines": "<lines>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNo
buyerYes
linesYes
notesNo
site_detailsNoPlant model, load, autonomy, ambient temperature (batteries)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses meaningful downstream behavior: the request is recorded and only quoted once a supplying factory is confirmed, nothing is binding, and nothing is sent automatically. That resolves the main ambiguity of a write-shaped call with openWorldHint. It does not warn that repeated calls are non-idempotent (a duplicate submission risk), which is the one notable omission.

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?

The action and audience come first, the fulfillment/liability caveats follow, and the consent constraint closes it. Dense but every clause carries information; there is little filler to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-idempotent submission tool with no output schema, the agent still does not know what it receives back (a confirmation, a request ID, or nothing) or whether a returned quote arrives via this channel. The description compensates well on process and consent but leaves the response contract and three of five parameters unexplained.

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 only 20%, but the description does cover the two required parameters in substance — line items as part numbers or descriptions with quantities, and buyer contact details subject to consent. It says nothing about the agent, notes, or site_details fields, leaving those to a schema that barely documents them.

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?

The description gives a specific verb and resource ('Record a sourcing requirement') and scopes it to a concrete population of buyers, so an agent can tell this is a submission action rather than a lookup. It never explicitly contrasts itself with the parts-search siblings, so the differentiation is inferential rather than stated.

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?

There is a clear precondition ('Only call with the buyer's consent to share their contact details'), which is genuine when-to-use guidance. However, there is no stated when-not-to-use, no pointer to search_parts/get_terms for resolving part numbers beforehand, and no guidance on how complete a requirement must be before recording it.

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