Skip to main content
Glama

get_methodology_guide

Read-onlyIdempotent

Survey-design best practices for academic research, mapped to Domandata fields: option and scale randomization, grids, sliders, conjoint, MaxDiff, tree tests, question order, follow-ups, Skip Rules, length, distribution, response-quality rules, piped text, and a pre-launch checklist. Static reference text; reads no survey. Without topic it returns the topic list and the checklist.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOne section to return (ids are listed in the response's topics), or "all" for the whole guide (about 28k characters).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive/closed-world behavior, and the description reinforces that by stating it is static reference text that reads no survey. It also warns that the whole guide is large (~28k characters via the schema) and that omitting topic yields a topic list plus checklist, which is real behavioral context beyond the annotations. No auth, rate-limit, or caching detail, but little is expected for a static doc tool.

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 core statement, then the scoping constraint and the no-topic fallback. The middle enumeration of topics is long but functional since it advertises coverage; the single-sentence list is dense yet readable.

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 an output schema present, return values need no explanation, and the description covers static-ness, scope, size, and default behavior. A bit more on freshness/versioning of the guidance would round it out, but nothing essential for correct invocation is missing.

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?

Schema coverage is 100% with an enumerated topic list, so the schema already carries parameter meaning. The description adds the useful default-behavior semantics absent from the schema: with no topic it returns the topic list and the checklist, and the enum ids are discoverable from the response's topics.

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 (survey-design best practices reference text) and its scope (mapped to Domandata fields), then explicitly negates the read behavior of siblings: "Static reference text; reads no survey." An agent can distinguish this from read_survey/create_survey without opening the schema.

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?

"Static reference text; reads no survey" plus the pre-launch checklist and the no-topic fallback make the usage context clear: consult this for guidance rather than to fetch survey data. It stops short of explicitly naming an alternative tool or stating a when-not condition, so it does not reach 5.

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