GeezerKeeper Referral Exit Routes and Deadlines

Get an unfilled stop-contact request template

get_unfilled_request_template

Read-onlyIdempotent

Return an unfilled template for a referral network or an identifiable provider. The server accepts no personal fields and never sends the request. Replace bracketed placeholders locally.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sourceId`	Yes	Used only to return the current source-specific destination and instructions
`recipientType`	Yes	Return a template for the referral network or for one identified provider

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sourceId`	Yes
`template`	Yes
`disclaimer`	Yes
`destination`	Yes
`dataBoundary`	Yes
`recipientType`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

The description adds valuable context beyond the annotations: 'The server accepts no personal fields and never sends the request' clarifies the privacy and non-transmission behavior, and 'Replace bracketed placeholders locally' tells the user what to do with the result. This supplements the readOnly and idempotent hints.

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?

The description is two sentences, tightly packed with essential information. It is front-loaded with the primary purpose and uses no filler words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has an output schema, and full parameter coverage. The description covers the core behavior, local handling, and safety guarantees, making it complete for the tool's complexity.

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%, with both parameters well-documented via enums and descriptions. The tool description does not significantly add meaning beyond the schema, so it stays at the baseline score.

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?

The description starts with 'Return an unfilled template for a referral network or an identifiable provider,' which clearly states the verb (return), resource (template), and target recipients. This distinguishes it from sibling tools like get_info or get_services.

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 description makes it clear that this tool is for obtaining a template that is filled locally, not for sending requests. It implies the intended use case but does not explicitly name alternatives or state when not to use it, so it falls 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.

All GeezerKeeper Referral Exit Routes and Deadlines tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

Most tools have clearly distinct purposes: get_info, get_location, get_services, lookup_deadline, lookup_exit_route, choose_workflow, and template retrieval are all separate concerns. However, get_info and get_services both touch on pricing/options, which could cause slight confusion.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (get_*, lookup_*, choose_*). The verbs are semantically appropriate, and the style is uniform throughout, making the set predictable.

Tool Count5/5

With 7 tools, the set is well-scoped for a niche informational server focused on referral exit routes and deadlines. Each tool covers a distinct aspect, and the count does not feel excessive or sparse.

Completeness4/5

The toolset covers key information retrieval (business info, services, location), lookup of deadlines and exit routes, and workflow selection. A minor gap is the lack of a tool to list all supported networks, which would improve discoverability, but agents can work around this.

Resources

Need Help?