Skip to main content
Glama

report_provider_availability

Idempotent

Report capability capacity for 60 seconds. Self-reported advisory only; does not reserve compute. Only the capability owner can report.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "capability_id": "<capability_id>",
      "capacity": "<capacity>",
      "max_concurrency": "<max_concurrency>"
    },
    "name": "report_provider_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
capacityYes
capability_idYes
max_concurrencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a 60-second validity window, the fact that the report is self-reported and does not reserve compute, and an ownership/auth constraint. What remains unstated is repeat-call behavior (does a second report overwrite the first and reset the TTL, consistent with idempotentHint=true) and any rate limits.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and TTL, followed by effect semantics and the auth constraint. No filler or redundant restatement of the name.

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 small write tool with no output schema, the description covers authorization, lifetime, and non-reserving semantics well. It is incomplete on the one thing that matters most here: what the three required numeric/string parameters mean and how capacity differs from max_concurrency.

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?

Schema description coverage is 0% across three required parameters, and the description supplies no parameter meaning at all. In particular the distinction between 'capacity' (0-100) and 'max_concurrency' (1-100) is genuinely ambiguous and is left entirely to the agent to guess.

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?

Uses a specific verb and resource ('Report capability capacity') plus a temporal scope (60 seconds), so the action is unambiguous. It does not distinguish itself from siblings such as publish_capability or market_status, leaving the agent to infer that this is a status broadcast rather than a listing/registration call.

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?

Gives clear operating context: the report decays after 60 seconds, it is advisory and does not reserve compute, and only the capability owner may call it. It stops short of naming an alternative for actually reserving compute, so the when-not side is implied rather than stated.

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