Skip to main content
Glama
Sign In

Polyrank

by io.github.polyrank
OverviewDiscussionsAdmin

Polyrank trader teasers (batch, by masked id)

polyrank_get_traders_batch
Read-onlyIdempotent

Fetch the free masked skill teaser for several traders at once by their opaque masked ids (tids). Same per-trader payload as polyrank_get_trader_by_tid, capped at 10 tids per call. No API key needed. Each result is tagged with its tid, and per-tid failures are returned inline (as an error field) rather than failing the whole batch.

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": {
      "tids": "<tids>"
    },
    "name": "polyrank_get_traders_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidsYesOpaque trader ids (tids) from masked rows (max 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, but the description adds genuinely new behavioral facts: no API key required, a hard 10-tid batch cap, per-tid failure isolation via an inline error field instead of whole-batch failure, and tid tagging on each result. These are exactly the operational details an agent needs before batching.

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?

Three compact sentences, front-loaded with the action and scope, with failure behavior last. Minor redundancy between "free" and "No API key needed" costs it a point but nothing else is wasted.

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

Completeness5/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 still conveys the return shape (per-tid tagged payloads matching the single-trader tool) and error semantics (inline per-tid error field). Nothing an agent needs to call and interpret this batch tool is missing.

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 100% and the single parameter already documents opaque tids with a max of 10. The description's "opaque masked ids (tids)" and "capped at 10 tids per call" restate the schema rather than adding format or sourcing guidance beyond it, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ("fetch the free masked skill teaser for several traders at once") and explicitly scopes it to batch-by-tid retrieval, distinguishing it from the single-item sibling polyrank_get_trader_by_tid. An agent can select it without opening either schema.

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

Usage Guidelines4/5

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

The phrase "for several traders at once" and the reference to "Same per-trader payload as polyrank_get_trader_by_tid" implicitly route the agent: batch here, single-tid tool there. It stops short of an explicit when-not statement (e.g. "use the single tool when you have one tid"), so it is clear but not fully prescriptive.

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

All Polyrank 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