Skip to main content
Glama

Agoranome buyer checks and market data

Rank sample (free)

rank_sample
Read-only

Free: the top three Bazaar results a buyer agent would see for a task, and your rank if you pass resource.

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": {
      "task": "<task>"
    },
    "name": "rank_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat a buyer agent is searching for
resourceNoYour listed resource URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful conditional behavior the annotations do not: only the top three results are returned, and the rank field appears only when `resource` is passed. It does not say whether "free" implies a call quota, rate limit, or truncation of the result list.

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?

A single tight sentence with the key qualifier ("Free") and the conditional rank behavior front-loaded. It is telegraphic to the point of slight awkwardness ("Free: the top three..."), but no sentence is wasted.

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?

With no output schema, the description carries the burden of describing returns, and it only sketches them: three results plus a rank. It does not say what fields the three results contain (name, URL, score, position) or how ranking is derived, which leaves an agent guessing about how to consume the response.

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 both parameters are already documented, making 3 the baseline. The description adds meaning beyond the schema by tying `resource` to a conditional output: passing it causes the response to include your own rank, which the schema's plain "Your listed resource URL" does not convey.

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 concrete verb and resource set: it returns the top three Bazaar results a buyer agent would see for a given task, plus the caller's rank when a resource is supplied. An agent can tell exactly what comes back, though it does not explicitly contrast itself with sibling lookup tools such as pick_odds or price_position.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The leading word "Free" implies this is a low-cost preview variant of some paid tool, but the agent must infer that and cannot tell from the text when the full/paid version is warranted instead.

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.