Skip to main content
Glama

Find pain science lessons

find_pain_lessons
Read-only

Searches Recalibrate Academy's library of chronic pain education lessons (pain science, nervous system, sensitization, sleep, emotions, flares, self-management) and returns the most relevant lessons with key takeaways. Use when the user wants to understand or learn about chronic pain or a related topic.

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": {
      "topic": "<topic>"
    },
    "name": "find_pain_lessons"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWhat the user wants to understand, e.g. 'why does my pain move around'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds useful context that this searches a specific lesson library across listed topic areas and returns relevant lessons with key takeaways, though it omits result count, ranking, and pagination details.

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?

Two sentences are front-loaded with the search behavior and followed by the use condition. The parenthetical topic list earns its place by clarifying coverage, and there is no redundant restatement of the title.

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-parameter read-only search tool with no output schema, the description covers the domain, use case, and the nature of returned lessons. It leaves minor gaps around result limits and the boundary with read_pain_lesson, but nothing essential to invoking it correctly.

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?

There is one parameter with 100% schema coverage, including a natural-language definition and example, so the schema baseline is 3. The description reinforces the topic scope by enumerating lesson categories, but it does not add format or constraint details beyond what the schema provides.

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 uses a specific verb ('Searches') and resource ('Recalibrate Academy's library of chronic pain education lessons'), and enumerates the topic areas covered. It does not explicitly name or contrast the sibling read_pain_lesson, so sibling differentiation is inferred from the search/return behavior 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 Guidelines4/5

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

It gives a clear use condition: when the user wants to understand or learn about chronic pain or a related topic. It does not state when not to use it or point to read_pain_lesson/check_pain_flare alternatives, so it stops short of explicit routing guidance.

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