Skip to main content
Glama

AutoTasker Hub — China Social Data API

themealdb

Recipe search (TheMealDB): ingredients, measures, instructions, thumbnail, YouTube link. $0.01 USDC.

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": {
      "query": "<query>"
    },
    "name": "themealdb"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add one genuinely useful non-schema fact: the call costs $0.01 USDC, which matters for a paid tool. It also enumerates returned fields, but it never says how matching works (name vs. ingredient), whether results are paginated, or what an empty result looks like.

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?

One sentence, front-loaded with the action and the source, followed by the payload fields and cost. No filler, no repetition of the name or title.

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

Completeness3/5

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

The absence of an output schema makes the field list valuable, and the cost disclosure is a real addition. But for a one-parameter paid search tool, leaving the query's semantics and matching behavior undefined is a meaningful hole the description should close.

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?

The single required parameter "query" has 0% schema description coverage, so the description is the only place its meaning could be established. It never says whether query is a meal name, an ingredient, or a free-text phrase, which is exactly the ambiguity an agent would hit first.

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?

"Recipe search (TheMealDB)" gives a specific verb and resource plus the data source, and the field list (ingredients, measures, instructions, thumbnail, YouTube link) makes the payload concrete. It is distinguishable from the sibling set, none of which appear to be recipe tools, though it does not explicitly rule anything out.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no statement about what the query should look like, and no routing to alternatives. The only contextual signal is the price, which tells the agent it costs money but not when that cost is warranted.

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.