Skip to main content
Glama
Sign In

PokéItem

by fr.pokeitem
OverviewDiscussionsAdmin

Preview a trade

trade_preview
Read-only

Preview a trade vs another trainer's public profile slug (/u/{slug}). Uses their share settings. Returns top 15 cards you could give/receive with PokéItem fair values — never marketplace listings.

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

Input Schema

NameRequiredDescriptionDefault
slugYesPublic profile slug

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?

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it relies on the target user's share settings (a visibility/permission dependency) and caps results at the top 15 cards with PokéItem fair values. Not stated: behavior when the profile's share settings restrict viewing.

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

Conciseness5/5

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

Two compact sentences, front-loaded with the action and target, then the return contents and the explicit exclusion. No filler or repetition.

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?

With no output schema, the description usefully summarizes the return (top 15 give/receive cards with fair values) and rules out marketplace data. Remaining gaps are minor: no mention of error behavior for private/restricted profiles or whether results are paginated.

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 100%, so baseline is 3, but the description adds meaning the schema lacks: the slug belongs to another trainer and maps to the /u/{slug} route, and the preview is computed under that user's share settings. This clarifies the value's provenance and constraints.

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 ('Preview') and resource ('a trade') with the exact target scope: another trainer's public profile slug. The clause 'never marketplace listings' further pins down what this is not. It does not name a sibling tool such as deal_check, so it stops short of full differentiation.

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?

Usage is implied by 'preview a trade vs another trainer's public profile slug', but there is no explicit when-to-use or when-not guidance and no pointer to the alternative (deal_check) for price/marketplace comparison. The 'never marketplace listings' note is about output content, not about choosing the tool.

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

All PokéItem toolsInspect
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