Skip to main content
Glama

Little Works

list_coverage

Coverage map for AI buyers — density of certified outcomes by place × trade (sales artifact).

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

Input Schema

NameRequiredDescriptionDefault
tradeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not say whether the data is live or static demo content, whether it is read-only, how large the result is, or what shape the response takes; "sales artifact" gestures at provenance but is too terse to constitute real behavioral disclosure.

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?

It is a single short sentence with no filler, and the subject (coverage map) is front-loaded. The trailing parenthetical is mild noise, but nothing is bloated.

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

Completeness1/5

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

With no annotations, no output schema, and an entirely undocumented parameter, this one-liner leaves too much unknown for an agent to invoke the tool correctly. It does not convey what fields come back or how the trade filter behaves, which is the minimum needed here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter has 0% schema description coverage, and the description only echoes "trade" as a coverage dimension without explaining accepted values, format, or whether omitting it returns all trades. It adds little meaning beyond the schema, leaving the filter semantics to inference.

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 description names a specific resource (a coverage map of certified outcomes by place × trade) and implies a list-style read, but the phrasing is jargon-heavy ("certified outcomes," "sales artifact") and it never states plainly that it returns coverage entries. It does not distinguish itself from plausible siblings such as list_materials_places or discover_capabilities, so an agent cannot confidently choose it over those.

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 when-to-use guidance, no prerequisites, and no named alternative. The parenthetical "(sales artifact)" hints at a demo/marketing context but does not tell an agent under what conditions this tool should be preferred over the other list_* tools.

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