Skip to main content
Glama

query_pgaplayerpage

Read-only

Added after you connected: the first call asks you to approve it. Find PGAPlayerPage records - pass id for one record, or query for a filtered list.

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

Input Schema

NameRequiredDescriptionDefault
idNoFetch one record by id; omit to query many
skipNoRecords to skip before the first result; 0 or more.
sortNoSort field; '-' prefix for descending
limitNo1-500; defaults to 50. Out-of-range values are clamped.
queryNoMongoDB-style filter, e.g. {"status": "active"}
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and nothing in the description contradicts that. The description adds one genuinely useful behavioral note about an approval prompt on the first call, but it says nothing about the shape of returned records, pagination behavior beyond the schema, or rate limits.

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

Conciseness4/5

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

Two sentences, no filler, and the id-or-query rule is stated compactly. The opening connection/approval sentence is oddly placed ahead of the actual purpose statement, which delays the most important information slightly.

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

Completeness3/5

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

For a 6-parameter, read-only query tool with no output schema, the description covers the primary decision (id vs. query) but leaves return-value expectations unaddressed. An agent knows how to call it but not what a PGAPlayerPage record contains or how results are ordered by default.

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 83%, so most parameters (id, skip, sort, limit, query) are already documented in the schema, including defaults and clamping. The description reinforces the id-vs-query split but adds no meaning for sort, skip, limit, or fields beyond what the schema states, so the baseline of 3 applies.

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 names a specific verb and resource ('Find PGAPlayerPage records') and immediately splits the behavior into two call modes (single record by id vs. filtered list by query). It is clear enough to separate from create/update/delete siblings by the 'Find' verb alone, though it never explicitly contrasts itself with query_testimonial-style siblings.

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

Usage Guidelines3/5

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

It states the two usage modes ('pass id for one record, or query for a filtered list'), which implies when each parameter applies. There is no guidance on when not to use it, no mention that it should not be used for writes (create/update/delete siblings exist), and no exclusions or prerequisites.

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