Skip to main content
Glama

delete_pgaplayerpage

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

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": {
      "id": "<id>"
    },
    "name": "delete_pgaplayerpage"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a destructive operation but never says whether deletion is permanent, whether it cascades, whether it errors when the id is absent, or what permissions are required. The one genuinely useful disclosure, that the first call triggers an approval prompt, is phrased ambiguously and reads as injected metadata rather than deliberate documentation.

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 second sentence is tight and well-formed. The first sentence, about being added after connection and requiring approval, is front-loaded but semantically murky and competes with the actual purpose; it should either be stated clearly as a confirmation flow or removed.

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 an irreversible mutation tool with zero annotations, no output schema, and an undocumented parameter, the definition should explain permanence, failure modes, and the approval flow. It gestures at the approval step but leaves the destructive semantics and return behavior entirely unstated.

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 0% for the single id parameter, but the description says 'by id', which at least conveys that the parameter identifies the target record. It adds nothing about format, source of the id (e.g. from query_pgaplayerpage), or behavior when the id does not match an existing record.

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 resource: 'Delete a PGAPlayerPage record by id.' That is enough to distinguish it from the create/query/update siblings without opening their schemas. The preceding sentence about approval is unrelated clutter rather than purpose.

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 guidance on when to use this versus query_pgaplayerpage, update_pgaplayerpage, or how to confirm the right record before destroying it. It is implied only by the tool name and the word 'Delete'; nothing states prerequisites or exclusions.

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