Money You're Owed Catalog
Server Details
Informational Q&A: money owed to consumers (deposits, claims, unclaimed funds). No debt relief.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of confusion between tools.
Only one tool exists, so naming consistency is not an issue; the name 'answer_money_question' is descriptive.
A single tool for a 'catalog' is too few; users would expect multiple tools for browsing or searching different types of money-related information.
The single tool only answers questions, but there are no tools for listing categories, searching, or retrieving educational resources independently, leaving significant gaps.
Available Tools
1 toolanswer_money_questionAnswer a money-recovery questionARead-onlyInspect
Look up verified, source-cited facts and a linked educational resource for a consumer money-recovery question (security deposits, denied refunds, denied insurance/warranty claims, unclaimed property). Read-only lookup: it does not collect personal data, make payments, or change anything.
| Name | Required | Description | Default |
|---|---|---|---|
| question | Yes | The consumer's question in plain language, e.g. 'my landlord kept my security deposit' |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds value by explicitly stating that the tool does not collect personal data, make payments, or change anything—context beyond the annotations. This effectively clarifies the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two concise sentences. The first sentence efficiently states the purpose and scope with examples; the second clarifies behavioral constraints. No unnecessary words, and important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity (1 parameter, no output schema, no sibling tools), the description provides complete context. It covers the domain, the type of answers provided, and the read-only nature. No gaps remain for an agent to safely invoke the tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already covers 100% of the parameter with a clear description. The tool description adds only a brief example phrase ('e.g. 'my landlord kept my security deposit''), which provides minimal additional meaning. Baseline 3 is appropriate given high schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: looking up verified facts and educational resources for consumer money-recovery questions. It specifies the domain (security deposits, denied refunds, etc.) and uses a specific verb 'look up' combined with a resource type. No sibling tools to differentiate from, but it is highly specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While there are no explicit when-not-to-use instructions or alternatives (since no siblings), the description clearly implies when to use the tool: for consumer money-recovery questions. The read-only clarification helps set expectations. Slightly limited exclusions prevent a perfect score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!