Skip to main content
Glama

VOLT48 — 48V DC telecom power

Supply terms

get_terms
Read-onlyIdempotent

Where VOLT48 stands today (selecting manufacturing partners, no orders yet), condition policy, markets, compliance and contacts.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description's only addition is the topical scope of the returned content (standing, policy, markets, compliance, contacts), which is useful given there is no output schema, but it says nothing about format, freshness, or authority of the terms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and contains no padding, but it is a sentence fragment starting with 'Where', which delays comprehension and gives no verb up front. A single leading verb would make the same content clearer.

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 zero-parameter read tool with no output schema, the description does sketch the returned topics, which is the main thing an agent needs. It stops short of stating whether these are static terms, current status, or contact details, and never tells the agent what question this tool answers.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add or omit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The text names the resource ('Where VOLT48 stands today... condition policy, markets, compliance and contacts') but never supplies a verb such as 'get' or 'return', so the agent must infer from the title 'Supply terms' that this is a fetch. It reads as a content summary rather than a statement of what the call does, and nothing separates it from siblings like get_family or search_parts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no indication of when to call this versus request_quote or search_parts, nor any prerequisite or exclusion. The agent is left to guess that this is background/terms context rather than a lookup of specific records.

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