Skip to main content
Glama

Request Spec

request_spec

Logs a request for a spec that doesn't exist yet and notifies maintainers. Call this when a user asks for a provider or capability that has no spec in the registry (check list_providers first), or needs a capability in a country where no listed provider offers it (search_specs with country first). This helps maintainers prioritize which specs and providers to add next.

Args:

  • capability (string): Capability name e.g. "create_payment", or what is needed e.g. "ussd"

  • provider (string?): Provider slug e.g. "wave" — omit when no provider is named

  • country_code (string?): ISO 3166-1 alpha-2 code e.g. "SN" — required when provider is omitted

  • follow_up ("none" | "github_issue", default "none"): "none" records the request only; "github_issue" also returns issue_url, a pre-filled GitHub issue the user can review and submit

Returns: { logged: true, count, issue_url? } if the request was recorded — count is the all-time number of times this provider + capability (or, without a provider, capability + country) was requested, including this one (a repeated request counts again). count is absent if it could not be determined: do not guess a number. issue_url only with follow_up "github_issue": give it to the user, who submits it. { logged: false, reason: "spec already exists" }: the spec is in the registry — use the existing spec (get_spec) instead. isError if the request could not be stored: tell the user it was NOT recorded.

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": "<capability>"
    },
    "name": "request_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoProvider slug e.g. "wave"
follow_upNo"github_issue" also returns issue_url, a pre-filled GitHub issue the user can submitnone
capabilityYesCapability name e.g. "create_payment", or what is needed e.g. "ussd"
country_codeNoISO 3166-1 alpha-2 country code e.g. "SN" — required without provider

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / capability / description
      Previous value: -"Capability name e.g. \"create_payment\""New value: +"Capability name e.g. \"create_payment\", or what is needed e.g. \"ussd\""
    • addedInput schema / properties / country_code
      Added value: +{
      +  "description": "ISO 3166-1 alpha-2 country code e.g. \"SN\" — required without provider",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / follow_up
      Added value: +{
      +  "default": "none",
      +  "description": "\"github_issue\" also returns issue_url, a pre-filled GitHub issue the user can submit",
      +  "enum": [
      +    "none",
      +    "github_issue"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "provider",
      -  "capability"
      -]New value: +[
      +  "capability"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile; the description adds the side effect of notifying maintainers, count semantics (all-time, repeated requests count again, absent if indeterminate — 'do not guess a number'), and failure behavior (isError means not recorded). It also explains that issue_url is for the user to submit, which the openWorldHint annotation alone would not convey.

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?

Front-loaded with purpose and routing guidance, then a tidy Args/Returns block. It is longer than most definitions but nearly every sentence carries information an agent needs; the Returns section could be tightened slightly.

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?

There is no output schema, and the description fully compensates by documenting both success shapes ({logged: true, count, issue_url?} and {logged: false, reason}), plus the isError case. Conditional parameter rules are also covered, so an agent can call this correctly without inference.

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 100%, so the baseline is 3, but the description adds cross-field logic the schema does not express: country_code is required when provider is omitted, and provider should be omitted when none is named. It also clarifies follow_up's effect on the return value rather than just restating the enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb plus resource: 'Logs a request for a spec that doesn't exist yet and notifies maintainers.' It also states the outcome (helps maintainers prioritize), which distinguishes it from read-only siblings like get_spec and search_specs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions with prerequisite checks ('check list_providers first', 'search_specs with country first') and a when-not path routing to get_spec if the spec already exists. Alternatives are named rather than implied.

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.