Skip to main content
Glama

LiftBrain Library

Get guide

liftbrain_get_guide
Read-only

A guide's full text as Markdown, in the language asked for when it is translated, else in English.

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": {
      "slug": "<slug>"
    },
    "name": "liftbrain_get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesFrom liftbrain_list_guides
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
Behavior4/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 safety is covered. The description adds real behavior beyond that: the response is Markdown and there is a language fallback to English when a translation is unavailable, which an agent needs in order to interpret results correctly.

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?

One sentence, front-loaded with the return format and then the language rule. The phrasing 'in the language asked for when it is translated' is slightly contorted but conveys the conditional without padding.

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 simple two-parameter read tool with full schema coverage and annotations covering safety, the description covers what is returned and how language selection resolves. It lacks only edge-case information such as behavior for an unknown slug or the size of the returned Markdown, which are minor for this complexity level.

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 both parameters are documented in the schema, including the accepted language codes, so the schema carries the load. The description only reinforces the language parameter with the fallback rule (requested language if translated, else English), which adds modest meaning beyond the schema text.

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 the specific resource (a guide) and states the exact return format ('full text as Markdown'), so the agent knows this is a content-retrieval tool rather than a list or search. It does not explicitly contrast itself with liftbrain_get_recipe, but the resource noun is unambiguous.

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 statement of when to use this tool versus liftbrain_list_guides or liftbrain_search_recipes. The only routing hint ('From liftbrain_list_guides') lives in the schema for the slug parameter, not in the description itself.

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