RxRooster

Find a city for a job shortlist

resolve_shortlist_location

Read-onlyIdempotent

Resolve an explicitly supplied US city and state for an approximate distance search. Use only after the user supplies a place. Return the city for review; do not substitute a guessed location or state capital. Explicit lookup, not autocomplete.

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": {
      "query": "<query>"
    },
    "name": "resolve_shortlist_location"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Output Schema

Name	Required	Description	Default
`note`	Yes
`status`	Yes
`location`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds real behavioral constraints beyond them: the input must be explicit, and the agent must not guess or fall back to a state capital. It adds no detail on failure behavior for an unresolvable query, which is the remaining gap.

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 short sentences, front-loaded with the purpose and ending on the key constraint. The fragment 'Explicit lookup, not autocomplete' is slightly clipped, but every sentence carries distinct information with no filler.

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 one-parameter, read-only lookup with a rich annotation set and an output schema, the description supplies the preconditions and the anti-guessing guardrails an agent needs. Nothing critical is missing, though a note on unresolvable queries would make it airtight.

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 0% and the single parameter is just 'query' with length bounds, so the description carries the burden. It specifies the query must be a US city plus state and must come from the user, which meaningfully constrains what goes in that string.

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 concrete verb and resource ('Resolve ... US city and state') and frames the output purpose ('for an approximate distance search'), so the agent knows exactly what it gets back. It stops short of naming a sibling tool, but the closing 'Explicit lookup, not autocomplete' rules out the closest confusable behavior.

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?

'Use only after the user supplies a place' is an explicit precondition, and 'do not substitute a guessed location or state capital' is a clear negative constraint on when this tool is appropriate. No sibling is named as an alternative, which keeps it out of the top score band.

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

All RxRooster tools Inspect

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

Need Help?