Skip to main content
Glama

Read the method

get_method

Retrieve the Life Compass method's rules and ordered questions or steps for each phase, including why each matters; pass a phase to return only that section.

Instructions

Returns the Life Compass method: rules and, for each phase, the questions or steps in order with the reason for each. Pass a phase to get just that part.

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

Input Schema

NameRequiredDescriptionDefault
phaseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the shape and content of the result (rules, ordered questions/steps, rationale per item) and that a phase narrows the output, but it never says the operation is a pure read with no side effects, nor whether the content is static.

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 tight sentences: the primary return is front-loaded, the per-phase breakdown follows, and the optional-filter note closes. No filler or redundancy.

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 single-optional-parameter read tool with no output schema, the description covers payload content, ordering, and the effect of the parameter. The one gap is that return values are only characterized in the abstract rather than with any structural detail.

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 0%, so the description has to compensate: it does by explaining that omitting `phase` returns the full method while supplying one returns only that part, which the bare enum does not convey. The enum values themselves are self-explanatory phase names, so per-value meaning is unnecessary.

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?

"Returns the Life Compass method" pairs a clear verb with a named resource, and the rest of the sentence specifies the payload: rules plus per-phase questions/steps in order with reasons. An agent knows exactly what comes back. It does not name a contrasting sibling (e.g. get_plan), so it stops short of 5.

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?

The only usage-related sentence is "Pass a phase to get just that part," which is parameter behavior, not when-to-use guidance. Nothing states when to reach for this versus get_plan, get_status, or the review tools, and no preconditions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.