Skip to main content
Glama

Tidy Quid budget planners

Search Tidy Quid planners

search_products
Read-onlyIdempotent

List Tidy Quid digital budget planners and money trackers (Excel / Google Sheets / printable PDF) with price in GBP, country edition, language, what each does and the Etsy or Gumroad link. Filter by country (UK, US, DE, FR, AU, CA, PL), category, max price or free-text query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree text, e.g. 'council tax' or 'wedding'
countryNoUK, US, DE, FR, AU, CA or PL
categoryNo
max_price_gbpNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld=false, so the safety profile is covered. The description adds genuine context beyond that: the catalog contents, the GBP currency of prices, and that each result carries a purchase link to Etsy or Gumroad. It does not mention pagination or what happens when no products match.

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?

Two dense sentences, front-loaded with the resource and its return fields, followed by the filter surface. Parenthetical enumerations are compact and no sentence is wasted, though the country list is duplicated from the schema.

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 usefully spells out what a result contains (price, edition, language, purpose, purchase link). For a simple, parameterless-required, read-only search that is nearly complete; only result limits and empty-result behavior are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: query and country are documented in the schema, while category and max_price_gbp have no schema descriptions. The description only restates those filters in prose and repeats the country code list already present in the schema; it never clarifies the category enum values or confirms that max_price_gbp is a strict upper bound with a free-tier boundary. It adds almost no meaning beyond the structured fields.

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?

The description names a specific verb (list/search) and resource (Tidy Quid digital planners in Excel, Sheets and PDF), and even enumerates the fields returned (price in GBP, country edition, language, description, Etsy/Gumroad link). That makes it clearly a catalog-browsing tool rather than a recommender, although it never explicitly contrasts itself with the sibling recommend_planner.

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?

It lists the available filters and the accepted country codes, which implies how to narrow results, but it gives no guidance on when to choose this over recommend_planner or the UK-specific tools, and no note on behavior with no filters applied.

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