Skip to main content
Glama

Upgrade Price

upgrade_price
Read-onlyIdempotent

The price of one upgrade (CCU) from one ship to another: the standard price, and the warbond price when RSI's store has one now. One step only.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "upgrade_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe ship the upgrade ends at
fromYesThe ship the upgrade starts from

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful behavior beyond that: it returns two price values, the warbond price is conditional on current store availability (implying it can be absent), and the lookup covers only a single upgrade step rather than a chain.

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?

Two short sentences, front-loaded with the resource and with no filler; 'One step only' is terse but earns its place as a scope limit. The colon-and-list construction is slightly awkward but not wasteful.

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?

For a read-only two-parameter price lookup with no output schema, the description covers the essential return content (standard and warbond prices) and the conditional nature of the warbond value. Minor gaps remain: it does not say how ships are identified (name vs. ID) or what happens if no upgrade exists.

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 both parameters are documented as start and end ship, so the schema already carries the semantics. The description only restates 'from one ship to another' without adding format or lookup details, which is the baseline 3 case.

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 specific resource (upgrade/CCU price) and scope (one ship to another, standard plus warbond), which is more precise than a generic 'get price'. It does not name any sibling tool, but 'One step only' implicitly distinguishes it from chain-style comparisons; a clearer contrast with store_now or compare_ships would push this to a 5.

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 'when RSI's store has one now' clause describes data availability, not invocation guidance, so an agent must infer the tool's niche from context alone.

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.

Resources