Skip to main content
Glama

The research method (the skill), in sections

research_guide
Read-onlyIdempotent

How to research this corpus well - the procedure, the text-field rules, what each call costs, caution handling, citing. Free. Call it with section "start" FIRST, once per conversation, before any search: section "start" (the default) is the part to read first and lists the others; "api" has every field and filter, "caveats" the traps, "examples" twelve worked investigations, "display" how to present results, "research-folder" the per-topic folder. Returns markdown, never search results.

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

Input Schema

NameRequiredDescriptionDefault
sectionNostart

Output Schema

NameRequiredDescriptionDefault
textYesMarkdown. Read it and follow it.
charsYesLength of `text`
sectionYesThe section returned
versionYesContent hash of the whole skill; changes when the method changes
sectionsYesEvery section, so you can ask for the one you need

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world safety, so the bar is lower. The description still adds material context beyond them: the call is free, it is meant to be read once per conversation rather than repeatedly, and it returns markdown rather than search results. Minor gap: it does not say how large the sections are or whether a section can be re-read after the first call.

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?

Front-loaded with the imperative 'Call it with section "start" FIRST' and every clause earns its place. The semicolon-chained section list is dense and reads as a run-on, which costs a little scannability, but nothing is redundant.

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

Completeness5/5

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

An output schema exists, so return values need no explanation, and the description still notes the markdown format. For a one-parameter documentation tool, an agent has everything needed to call it correctly at the right moment.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the enum, and it does: 'start' is identified as the default and the index of the others, 'api' as every field and filter, 'caveats' as traps, 'examples' as twelve worked investigations, 'display' as presentation guidance, and 'research-folder' as the per-topic folder. That fully compensates for the undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: a method/skill guide covering procedure, text-field rules, per-call costs, caution handling, and citing. It also explicitly separates itself from the sibling search tools with 'Returns markdown, never search results,' so an agent can tell instantly this is documentation, not retrieval.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: call with section 'start' FIRST, once per conversation, before any search. It also routes within the tool by listing what each section contains, so selection among the enum values is fully determined.

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