Skip to main content
Glama

Top-rated recipes

liftbrain_top_recipes
Read-only

The ten recipes LiftBrain's athletes rate best in the app (1 to 5 stars, weighed by how many rated), with their rating and kcal and macros per serving.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world, so the safety profile is covered. The description adds real behavioral value beyond them: the result is capped at exactly ten, ranking is weighted by rating count, and each item returns rating plus kcal and macros per serving.

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?

A single front-loaded sentence with no filler; scope and ranking method come first and the returned fields follow. Minor cost: the phrase 'weighed by how many rated' is slightly loose wording for a weighted-average rule, costing a point of crispness.

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 parameters, no output schema, and annotations covering safety, the description carries the remaining burden well by naming the returned fields and the ten-item cap. It leaves only marginal questions open, such as whether the list is static or recomputed, which are unlikely to block a correct call.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. The parenthetical explains the scoring semantics of the returned data rather than any input.

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?

States a specific result set ('the ten recipes...rate best') and the ranking rule (1-5 stars, weighted by number of ratings), plus what each entry carries (rating, kcal, macros per serving). It is clearly distinguishable from search_recipes or get_recipe in spirit, but never names those siblings, so differentiation is inferred rather than stated.

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 guidance and no named alternative. An agent must infer that this is for 'show me the best recipes' while liftbrain_search_recipes is for filtering — the description supplies none of that routing logic.

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.