METODIC

Session run-sheet

get_session

Read-onlyIdempotent

READ a session so YOU know what is in it before answering a follow-up — this returns text for you, not something the user sees. To SHOW the session to the user, call session_one_pager instead. Gives every activity's agenda slot, method, step-by-step instructions, facili — every activity's agenda slot, method, step-by-step instructions, facilitator tips and materials. Plus a Metodic link for the branded/editable version. Use this to show a session's runnable detail without leaving the chat.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_session"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	The Metodic session (toolkit) id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuinely useful non-annotation context: the output is text for the agent, not the user, plus the contents returned and a Metodic link. The contradictory 'show the session' sentence slightly blurs this.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loading is good, but the description contains a visibly truncated duplicate ('facili — every activity's agenda slot, method, step-by-step instructions,') and a closing sentence that repeats and contradicts the opening. These defects mean not every sentence earns its place.

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?

No output schema exists, so the description must describe return values, which it does: agenda slots, methods, step-by-step instructions, facilitator tips, materials, and a Metodic link. Combined with read-only annotations this is largely complete, though the self-contradictory display sentence leaves an ambiguity about intended use.

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 description coverage is 100% and there is a single required parameter (session_id) already documented in the schema. The description adds no syntax, format, or sourcing detail for session_id beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb (READ) and resource (a session) and explicitly distinguishes itself from the sibling session_one_pager. However, the closing line 'Use this to show a session's runnable detail' muddies the read-vs-display distinction the opening establishes, and a truncated duplicate phrase ('facili — every activity's agenda slot...') weakens an otherwise precise statement.

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?

Gives explicit when-to-use ('before answering a follow-up') and names the alternative with its triggering condition ('To SHOW the session to the user, call session_one_pager instead'). This is strong routing guidance, but the final sentence contradicts the stated use case by telling the agent to 'show' with this tool, undercutting the exclusion.

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

All METODIC tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?