Skip to main content
Glama

Open Agent Guide

Get Product Coverage

get_product_coverage
Read-onlyIdempotent

Read coverage, unknown scored fields, and evidence guidance before drafting.

Takes the same product identifier as get_product — exactly one of product (canonical), id, or the legacy product_id — so an agent that learned a spelling from one tool reuses it here without a retry.

Returns the catalog API response unchanged, including attested absences. Guidance and score projections do not corroborate proposed claims.

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_product_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoAlias for product, matching the REST {id-or-slug} route. Accepts a UUID or slug.
productNoThe product's UUID or slug.
product_idNoLegacy UUID-only argument. Use product instead.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety bar is low. The description still adds real behavioral value: the response is the catalog API response unchanged, it includes attested absences, and guidance/score projections do not corroborate proposed claims. That last caveat is an important interpretation constraint not available from structured fields.

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?

Three short paragraphs, each front-loading its point: what it returns, the identifier contract, then output caveats. Minor cost from backticked identifiers and the jargon of the opening line, but no filler sentences.

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

Completeness5/5

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

An output schema exists, so return values need no prose explanation, and the annotations carry the safety profile. The description fills the remaining gaps an agent needs: the one-of identifier rule, the unchanged-passthrough behavior, and how to treat projections versus attestations.

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?

Schema coverage is already 100%, but the description adds meaning the schema does not express: exactly one of product, id, or product_id must be supplied. The top-level schema has no oneOf/anyOf exclusivity constraint, so this is substantive added semantics, along with the rationale that spellings learned from get_product carry over.

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 and resource set: read coverage, unknown scored fields, and evidence guidance, with a clear pre-drafting purpose. It differentiates itself from get_product by anchoring to the same identifier contract. The term 'unknown scored fields' is somewhat opaque without domain knowledge, keeping it below a 5.

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?

'Read ... before drafting' gives a concrete sequencing cue for when to call it, and naming get_product as the identifier-sharing sibling helps an agent chain the two. There is no explicit when-not or statement of what to use instead if coverage is already known.

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