Skip to main content
Glama

Money You're Owed Catalog

Answer a money-recovery question

answer_money_question
Read-only

Look up verified, source-cited facts and a linked educational resource for a US consumer money-recovery question (withheld security deposits, airline refunds, unclaimed property, ticket-resale refunds, frozen fintech accounts). Read-only lookup: it does not collect personal data, make payments, or change anything.

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": {
      "question": "<question>"
    },
    "name": "answer_money_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe consumer's question in plain language, e.g. 'my landlord kept my security deposit'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; the description nonetheless adds concrete reassurance that it does not collect personal data, make payments, or change anything. It also describes the return content (source-cited facts plus a linked educational resource), which matters because there is no output schema. Missing details like latency or how many facts come back keep it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, zero filler. The capability and topic scope land first, followed immediately by the read-only guarantee, so both the what and the safety constraint are front-loaded.

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 no output schema, the description covers purpose, scope, input form, and the nature of the response. It would be fully complete if it said anything about how results are shaped when no verified answer exists or what the citation payload looks like.

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 coverage is 100% and the single "question" parameter already carries its own description with an example, so the schema does the heavy lifting. The description only implies that input is a plain-language question and adds no syntax, length or formatting guidance beyond that.

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?

Names a specific verb ("look up") and precise resource ("verified, source-cited facts and a linked educational resource"), then enumerates the exact domain scope (security deposits, airline refunds, unclaimed property, ticket-resale refunds, frozen fintech accounts). An agent can decide at a glance whether a user's question falls inside this tool's coverage.

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?

The enumerated topic list functions as a clear when-to-use signal, and "US consumer money-recovery question" bounds the applicable audience. There is no sibling tool to route against and no explicit "do not use for X" exclusion, which keeps it just short of a 5.

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