Skip to main content
Glama

NS Pros MCP Gateway

golfcore__api_account

For a developer using the GolfCore Course Data API: list the API accounts the signed-in person can see, or read one with its plan, this month's usage, monthly cap if one is set, and keys (prefixes only, never secrets). Use it before the other api_ tools to get account_id and key_id. Plans: free, 500 requests a month at 10 a minute; basic, $10 a month for 10,000 at 60 a minute, then $2.00 per 1,000; business, $50 a month for 100,000 at 300 a minute, then $1.00 per 1,000. Paid plans have no monthl

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

Input Schema

NameRequiredDescriptionDefault
account_idNoOptional. One account's detail; omit to list all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful behavior: visibility is scoped to accounts the signed-in person can see, and keys are returned as prefixes only, never secrets. It does not explicitly state read-only/non-destructive semantics or auth requirements, and the ending is truncated mid-sentence about paid plans.

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

Conciseness3/5

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

The purpose and usage guidance are front-loaded well, but the embedded pricing table is a substantial digression for a tool description and the text is cut off mid-word at the end. Some plan context helps interpret the returned fields, but the block is longer than necessary.

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 one-parameter read tool with no output schema, the description adequately explains what listing versus reading returns, including plan, usage, cap, and key prefixes. The truncated final sentence and absent pagination/error behavior are minor gaps against the low complexity.

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% for the single optional account_id parameter, so the schema already explains that omitting it lists all accounts and supplying it returns one account's detail. The description reinforces this behavior but adds no syntax, format, or validation meaning beyond the schema.

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?

The description gives a specific verb and resource — list API accounts or read one account with plan, usage, cap, and key prefixes — and distinguishes the two modes (omit account_id to list, supply it to read one). An agent can tell exactly what this tool returns 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?

It explicitly says to use this before the other api_ tools to obtain account_id and key_id, which gives a clear workflow condition. It does not name when-not to use it or contrast with api_budget, but the prerequisite guidance is strong enough for correct sequencing.

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.