Skip to main content
Glama

NS Pros MCP Gateway

golfcore__api_create_key

Create a GolfCore Course Data API key for the signed-in person's account. Returns the secret once; hand it to the person to store in their server's configuration, and never put it in chat logs, code, a mobile app or browser code. Confirm the name with the person first.

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

Input Schema

NameRequiredDescriptionDefault
nameYesWhat the key is for, such as the server or app.
expiryNoDefault 90_days.
account_idYesFrom api_account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses that the secret is returned only once and is not retrievable later, and it enumerates concrete prohibitions (no chat logs, no code, no mobile app, no browser code). It also flags a human-in-the-loop confirmation requirement before creation — exactly the behavioral context an agent needs for a credential-minting tool.

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 sentences, front-loaded with purpose, then the one-time return behavior, then the pre-call confirmation. Every sentence adds distinct operational value with no redundancy.

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?

No output schema and no annotations, yet the description covers the return payload (a one-time secret), the security handling rule, and a prerequisite. Only minor gaps remain, such as whether name collisions are rejected or how the secret should be delivered to the person beyond 'not in chat logs'.

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 description coverage is 100%, including the expiry enum and its 90_days default, so the schema already does the heavy lifting and baseline 3 applies. The description adds meaning for `name` via the confirm-first instruction, but says nothing about `expiry` choice or how `account_id` should be obtained beyond what the schema already states.

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 a precisely scoped resource ('Create a GolfCore Course Data API key for the signed-in person's account'), so an agent knows exactly what is produced and under whose authority. It does not explicitly name a sibling (e.g. api_revoke_key as the inverse, api_account as the source of account_id), which keeps it just short of 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?

Gives concrete pre-call procedure: confirm the name with the person first, then hand them the secret for their server configuration. It does not say when to prefer this over alternatives like api_revoke_key or api_upgrade, so the routing guidance is implied rather than explicit.

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.