Skip to main content
Glama

Get search filters

get_filters
Read-onlyIdempotent

Use this when you need valid tag slugs for search_recipes, for example to filter by cuisine, course, diet or occasion. Without arguments returns every category with its tags; with category returns only that category's tags. Not needed for plain keyword searches. Without a linked account, the full list covers the featured categories and only tags that have public recipes.

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": "get_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoA category slug or id, e.g. 'cuisine' or 'diet'. Leave out to get all categories.

Output Schema

NameRequiredDescriptionDefault
statusNo
messageNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds behavior the annotations cannot convey: the no-argument vs. with-category return shape, and the important caveat that without a linked account the list is limited to featured categories and tags that have public recipes — a real scoping/coverage limitation. It stops short of describing pagination or error cases, but the output schema covers return structure.

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?

Front-loaded with the purpose and the calling scenario, then the argument branching, then the caveat — a sensible priority order with no filler. Slightly repetitive in restating the all-vs-one behavior that the schema also encodes, but every sentence carries information.

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?

A single optional argument, full annotation coverage, and an output schema mean the description needs only to cover purpose, routing, and behavioral caveats — all present, including the unauthenticated-account limitation. Only minor gaps remain (e.g. whether tags are stable identifiers or how large the list can get).

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 parameter already documents the slug/id form and that omitting it returns all categories. The description reinforces the omission semantics and ties 'category' to real filter dimensions (cuisine, course, diet, occasion), but adds no syntax or validation detail beyond the schema. Baseline 3 applies.

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 states a specific resource (valid tag slugs per category) and its concrete consumer ('for search_recipes'), plus the two return modes (all categories vs. a single category). This lets an agent distinguish it from search_recipes or get_recipe without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use ('when you need valid tag slugs for search_recipes, for example to filter by cuisine, course, diet or occasion') and an explicit when-not ('Not needed for plain keyword searches'). The branching on whether the category argument is supplied is also spelled out.

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