Skip to main content
Glama

List guides

liftbrain_list_guides
Read-only

LiftBrain's guides on strength training and nutrition (AI workout plans, progressive overload, protein, cutting and bulking, meal prep, counting calories), with their slug and page, in the language asked for.

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_list_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage code: en, ru, uk, pl, de, es, fr, it, pt-br, tr; English when left out or not translated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that by stating the response includes a slug and page, but says nothing about ordering, pagination, or total result size for a catalog listing.

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 that leads with the resource and appends return fields. The parenthetical topic enumeration is long but earns its place by letting an agent judge topical coverage without a call.

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?

For a one-optional-parameter read-only list tool with no output schema, the description covers what is listed and the shape of returned fields. The only meaningful omission is result-set size or ordering, which is minor at this complexity.

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?

Only one optional parameter and schema description coverage is 100%, with the schema already documenting the language codes and the English fallback. The description's phrase "in the language asked for" merely restates that behavior rather than adding format or fallback detail.

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?

Names the resource precisely (guides on strength training and nutrition) and even enumerates covered topics, plus states the returned fields (slug and page). It lacks an explicit verb and never names a sibling such as liftbrain_get_guide, so an agent must infer the list-vs-fetch distinction from names alone.

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 only implied: the mention of returning slugs suggests this is the discovery step before fetching a specific guide, and the topic list hints at what is covered. There is no explicit when-to-use, when-not-to-use, or reference to alternatives like liftbrain_get_guide.

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.