Skip to main content
Glama

What Suppliers Net covers

coverage
Read-onlyIdempotent

States and supplier categories with their supplier counts, and how many dated prices are current. Use it to pick a category or state that exists.

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 adds that the payload is aggregate coverage (counts of suppliers and of current dated prices) rather than raw records, which is the useful behavioral signal here. It says nothing about size limits, staleness, or whether counts are exhaustive.

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 short sentences, output shape first and the call-to-action second, with no filler. The first sentence is slightly overloaded and its opening word is ambiguous, which costs a point.

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?

With no parameters and no output schema, the description carries the full burden of describing the return value; it names the fields but not their granularity or ordering. For a simple zero-arg coverage tool that is nearly sufficient, though a concrete example of the returned structure would close the gap.

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?

Zero input parameters, so there is no parameter semantics to explain; the baseline applies. The description correctly implies a parameterless call by framing the output as a discovery aid.

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?

Names the specific content returned: state and supplier-category groupings with supplier counts, plus a count of current dated prices. The agent can tell this is a coverage/metadata tool rather than a data-retrieval one. Slight ambiguity in the opening phrase 'States and supplier categories', which can be misread as a verb, and no explicit differentiation from the siblings.

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?

'Use it to pick a category or state that exists' gives a concrete when-to-use condition: discover valid filter values before querying. It does not name an alternative sibling or say when not to use it, so it stops short of full routing guidance.

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