Skip to main content
Glama

Tidy Quid budget planners

Recommend a planner

recommend_planner
Read-onlyIdempotent

Pick the single best Tidy Quid planner for a person's country and need (e.g. 'Christmas', 'annual bills', 'self assessment', 'energy bills', 'wedding', 'Haushaltsbuch', 'budget familial'). Returns the match, why, cheaper or bundle alternatives and the store link.

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": {
      "need": "<need>"
    },
    "name": "recommend_planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the person wants to sort out, in their words.
countryNoUK, US, DE, FR, AU, CA or PL. Default UK.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the bar is lower, and the description adds real value by disclosing the response shape: the match, the reasoning, cheaper or bundle alternatives, and a store link. That return-content summary is the most useful thing it contributes beyond the structured fields, though it says nothing about what happens when no planner fits the need.

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 sentences, both earning their place: the first defines the selection, the second defines the return. The examples are parenthetical rather than bloating the main clause, keeping the action 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?

With no output schema, the description correctly compensates by summarizing the return contents, and for a two-parameter, read-only recommendation tool that covers the essentials. The only gap is the absence of any fallback behavior when nothing matches the stated need.

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%, so both parameters are already documented, establishing a baseline of 3. The description reinforces the semantics with sample needs and the country scoping, but adds no format or normalization guidance (e.g. whether a free-text need in another language is acceptable) beyond the schema.

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 verb and resource ('Pick the single best Tidy Quid planner') scoped by country and need, and the parenthetical examples ('Christmas', 'self assessment', 'Haushaltsbuch') make the resource concrete. The 'single best ... recommendation' framing separates it from a catalog search like search_products without needing to name it.

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?

Usage is implied: call this when someone needs one planner chosen for their country and situation. There is no explicit when-not guidance and no named alternative (e.g. 'use search_products if you want to browse rather than get one pick'), so the agent must infer the boundary from the recommendation framing.

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