Skip to main content
Glama
Procurement MCP

Procurement MCP

by belikh

health

Check which procurement marketplaces can run by listing whether each required API key is set and whether its source is verified, missing, degraded, or unsupported—without exposing secrets.

Instructions

Report which marketplaces can run, with no secrets.

Each marketplace has: ready (its key is set), missing (the unset key),
source (the API or actor it calls) and status. Status is verified (a live
run matched the parser), unverified (written from docs), degraded (returns
nothing without extra setup) or unsupported (no source yet).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden. It does add real behavioral value by guaranteeing the output is secret-free (safe to surface to a user) and by defining the four status values. However, it leaves a key ambiguity unresolved: whether calling it merely reads recorded state or triggers live marketplace checks, which affects latency and side effects.

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 definition is front-loaded with the core claim and then enumerates the returned fields and status vocabulary in compact parenthetical form. Every sentence carries information; the only friction is that the field list reads as a dense run-on rather than a scannable structure.

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

Completeness4/5

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

For a zero-argument diagnostic with an output schema, this is nearly complete: it explains the shape of each marketplace entry and the meaning of every status value, going beyond what the schema alone would convey. The remaining gap is whether the readiness/verification reflects cached configuration or a fresh live check.

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, which is the baseline-4 case. Nothing in the input schema needs clarifying, so there is no gap for the description to close.

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 opening sentence names a specific action and resource: reporting which marketplaces can run, plus the guarantee that no secrets appear in the report. That is far clearer than the bare name 'health', though it never explicitly contrasts itself with the search/deal siblings, so the agent must infer this is a diagnostics tool rather than one that returns marketplace data.

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?

Usage is only implied: an agent can deduce this is the tool to call when it needs to know whether a marketplace is configured and functional before searching. There is no explicit when-to-use statement, no prerequisites, and no statement about when this tool should be skipped in favor of another.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.