Skip to main content
Glama

create_pgaplayerpage

Added after you connected: the first call asks you to approve it. Create a PGAPlayerPage record.

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": {
      "player_id": "<player_id>",
      "full_name": "<full_name>"
    },
    "name": "create_pgaplayerpage"
  }
}

Input Schema

NameRequiredDescriptionDefault
full_nameYesPlayer display name
player_idYesInternal pga.pga_players.player_id; the :playerId in /pga-player/:playerId (canonical URL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

Annotations supply only destructiveHint=false and omit readOnlyHint, so the description must carry most of the behavioral burden. The one useful disclosure is that the first call triggers an approval prompt, but the sentence is cryptic ("Added after you connected") and says nothing about whether creation is idempotent, what happens on duplicate player_id, or what the call returns.

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?

It is short, but the ordering is poor: the ambiguous approval-prompt sentence precedes the actual purpose, so the reader hits procedural noise before learning what the tool does. Nothing is padded, yet the first sentence is vague enough that it does not clearly earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and annotations lacking readOnlyHint, the description should clarify the entity and the outcome of creation. Instead it leaves the nature of a PGAPlayerPage undefined and gives no sense of the response or side effects.

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% and both parameters are documented in the schema, including the canonical URL hint for player_id, so the schema does the heavy lifting. The description adds no meaning beyond it, which is the baseline-3 case for fully covered schemas.

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

Purpose2/5

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

"Create a PGAPlayerPage record" restates the tool name verbatim and adds no distinguishing detail about what a PGAPlayerPage is or what creating one accomplishes. It does not differentiate itself from siblings such as update_pgaplayerpage or create_testimonial beyond the bare entity name embedded in the tool name itself.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool rather than update_pgaplayerpage, query_pgaplayerpage, or delete_pgaplayerpage, and no prerequisites or exclusions. The only procedural note concerns an approval prompt, which is not usage guidance about choosing this tool.

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.

Resources