Skip to main content
Glama

NS Pros MCP Gateway

golfcore__subscribe_premium

Create a GolfCore Premium checkout link for the signed-in golfer. Premium adds the caddie in this connector and the GolfCore app, plus green contour maps, live wind and offline course packs. Plans: day_pass, $3 for 24 hours of Premium, one charge and no subscription, the popular choice for a golfer on the course today; plus_monthly, $10 a month; and plus_yearly, $100 a year. A first-time subscriber pays half for the first month or first year. Ask the golfer which plan they want before calling. R

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": {
      "plan": "<plan>"
    },
    "name": "golfcore__subscribe_premium"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYesThe plan the golfer chose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 meaningful work: it discloses that the output is a checkout link (not an immediate charge), that day_pass is a single non-recurring charge while the other plans are monthly/annual, and that first-time subscribers pay half for the first period. It leaves gaps around link lifetime, whether repeated calls create duplicate links, and what the agent should do after a link is returned.

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 is correctly front-loaded, but the plan/pricing sentence is long and semicolon-chained, and the text terminates mid-word with a stray 'R', indicating a truncated definition. The pricing detail earns its place for an agent presenting options, but the trailing fragment and dense clause structure cost clarity.

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 tool with no output schema and no annotations, the description supplies the essentials: what is created, the three plan choices, their prices, and the discount rule. The main shortfall is the missing description of what the returned checkout link is for and any constraints on sharing or expiry.

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 already 100% with an enum, so a baseline of 3 applies, and the description genuinely adds meaning on top: it attaches concrete prices ($3/24h, $10/month, $100/year), explains the non-recurring nature of day_pass, and flags half-price first-term pricing that no schema field conveys. That pricing context directly helps the agent explain options to a golfer.

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?

The description opens with a precise verb and resource: 'Create a GolfCore Premium checkout link for the signed-in golfer,' which is far more specific than a generic subscribe call and tells the agent this produces a link rather than charging directly. It does not, however, distinguish itself from plausible siblings such as golfcore__api_upgrade or the many other *_subscribe tools, so the sibling differentiator is left to inference.

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?

There is an explicit procedural prerequisite: 'Ask the golfer which plan they want before calling,' which governs how the agent should sequence the call. What is missing is any when-not-to-use guidance, e.g. what to do for a golfer who already has Premium or how this differs from a sibling upgrade path.

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.