Skip to main content
Glama

NS Pros MCP Gateway

golfcore__api_revoke_key

Revoke one of the signed-in person's GolfCore API keys. Requests with it are refused within about a minute, and it cannot be restored. Confirm the key's name and prefix with the person before calling.

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": {
      "account_id": "<account_id>",
      "key_id": "<key_id>"
    },
    "name": "golfcore__api_revoke_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_idYesFrom api_account's keys.
account_idYesFrom api_account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the propagation delay ('refused within about a minute') and irreversibility ('cannot be restored'), both of which are non-obvious and materially affect how an agent should act. It stops short of stating permission requirements or what happens if the key_id is invalid or already revoked.

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?

Two sentences, both earning their place: the first states the action and its consequences, the second the confirmation requirement. Front-loaded with the irreversible effect and the propagation window.

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 two-parameter irreversible mutation with no annotations and no output schema, the description covers the critical unknowns: permanence, timing, and a safety check. It could go further on error behavior and whether other keys or services are affected, but nothing essential for a correct call is missing.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, including the provenance hints pointing to api_account. The description adds only the instruction to verify name and prefix with the person, which is a workflow hint rather than added parameter meaning; baseline 3 applies.

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?

States a specific verb and resource ('Revoke ... API keys') scoped to 'the signed-in person's' keys, which cleanly separates it from the sibling creation and account-listing tools. An agent can identify this as the destructive key-management operation without opening the schema.

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?

The description gives a clear precondition for invocation ('Confirm the key's name and prefix with the person before calling'), which is the right guidance for an irreversible action. It does not name an alternative path, but no natural alternative exists among the siblings, so this is close to complete.

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.