Agent Shopping Tracker

Get player

get_player

Read-onlyIdempotent

Look up one tracker row by slug, such as walmart or etsy. Credit the Page URL in the result. Keep the note. It is uncertainty.

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": {
      "slug": "<slug>"
    },
    "name": "get_player"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Player slug, such as walmart or etsy.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the bar is low, yet the description's additions are opaque: 'Credit the Page URL in the result. Keep the note. It is uncertainty.' conveys no actionable information about what is returned or what 'the note' means, and 'It is uncertainty' is uninterpretable.

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 and front-loads the lookup action, which is good, but the trailing sentences ('Keep the note. It is uncertainty.') are cryptic filler rather than compressing useful information. Brevity here comes at the cost of clarity.

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 one-parameter lookup with no output schema, the description should clarify what a 'tracker row'/'player' is and roughly what the result contains; the Page URL mention hints at this but the note/uncertainty fragments muddy it. Key context is missing or confusing.

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 the description merely repeats the slug example already present in the schema. No additional meaning (format constraints, case sensitivity, lookup failure behavior) is added, 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?

States a specific verb and resource: 'Look up one tracker row by slug', with concrete examples ('walmart or etsy'). It distinguishes a single-record lookup from the sibling list_players by saying 'one tracker row', though it never uses the tool's own vocabulary ('player'), leaving a small naming gap.

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?

Implies lookup-by-identifier usage but gives no explicit when-to-use or when-not-to-use guidance, and never mentions alternatives such as list_players for enumeration. The agent must infer that this is the single-record path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Shopping Tracker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?