Skip to main content
Glama

In Store

store_now
Read-onlyIdempotent

What RSI's pledge store sells right now, cheapest first, with what stands out about each (Warbond, Discounted, Limited, or Just Listed). Filter by type (ships, upgrades, or paints), warbond, or limited.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "store_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNo

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 readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuine behavioral detail beyond that: results are current store state, sorted cheapest first, and each item is annotated with why it stands out (Warbond, Discounted, Limited, Just Listed). It doesn't say how fresh the data is or how the tag set is determined, which keeps it from a 5.

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 tight sentences with the core scope and sort order front-loaded, followed by filtering options. Dense and mostly waste-free, though the parenthetical tag list and the filter sentence could be trimmed slightly.

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 two-parameter, read-only listing tool with no output schema, the description conveys what is returned (store items with highlight tags), ordering, and filter dimensions. The one material gap is the undocumented 'limit' parameter, which an agent must infer from the schema alone.

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%, so the description must carry parameter meaning. It enumerates the meaningful filter values (ships, upgrades, paints, plus warbond and limited) but omits 'all' and never mentions the 'limit' parameter or its 25 cap, leaving half the inputs unexplained.

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 resource ('RSI's pledge store') and scope ('sells right now'), plus ordering ('cheapest first') and the tag taxonomy (Warbond, Discounted, Limited, Just Listed). That is enough to distinguish it from siblings like sale_calendar, sale_history, or ship_details, which cover past events or per-ship data rather than a live listing.

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?

The second sentence gives filtering options, implying when to narrow results, but it never states when to use this tool versus sale_calendar/sale_history/compare_ships, nor any exclusions. Usage is implied rather than directed.

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