Skip to main content
Glama
SpeedyIndex MCP server

SpeedyIndex MCP server

Cost of the next check

rank_cost
Read-only

Calculate the token cost for a project's next position check and reserve the maximum amount while the check runs.

Instructions

What the project's next position check can cost, in tokens (cost.max is held while it runs).

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": {
      "project_id": "<project_id>"
    },
    "name": "rank_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 openWorldHint=true, so the safety profile is covered. The description adds the useful detail that the value is in tokens, but the parenthetical 'cost.max is held while it runs' is cryptic — it does not explain what 'held' means (a reservation? a budget cap?) or when it is released.

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?

One short sentence that front-loads the core meaning (cost in tokens) before the caveat. It is efficiently sized, though the trailing parenthetical is under-explained rather than wasteful.

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?

There is no output schema, so the description must convey the return shape; it says 'in tokens' but not whether the response is a scalar, a range, or an object with a max field — and the meaning of cost.max is left ambiguous. For a simple read-only estimate tool this is close to adequate, but the ambiguity around the held budget leaves a real gap.

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 0% for the single project_id parameter, but the parameter is self-evident and the description adds the relevant scoping concept ('the project's next position check'). No syntax or identifier-format guidance is given, so it neither compensates for nor worsens the schema gap.

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 resource and quantity: the token cost of the project's next position check. That is enough to tell it apart from rank_run_check (which performs the check) and rank_projects (which lists projects), though the description never names those siblings explicitly.

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 only implied: the phrase 'next position check' hints that this is called before rank_run_check to preview token spend. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the workflow from the word 'next'.

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