Skip to main content
Glama
Sign In

METODIC

by io.metodic
OverviewDiscussionsAdmin

Find a proven session format

find_session_format
Read-onlyIdempotent

START HERE when someone describes a PROBLEM or CHALLENGE ('our leadership team works in silos', 'nobody speaks up in retros', 'we need to align on strategy') and wants a session for it. Returns proven, ready-made session formats from Metodic's catalogue: the problem each one solves, who it is for, how long it runs, what it produces, WHY it works, and the named methodology it is built on. These are designed formats, not improvised ones — recommend from these before proposing a structure of your own, and name what each is grounded in. Free and instant. When the user picks one, call design_session with its format_slug.

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": {
      "challenge": "<challenge>"
    },
    "name": "find_session_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
audienceNoOptional: who is in the room, e.g. 'executives', 'agile teams', 'teachers'.
languageNoOptional ISO code (en, nl, es, ja). Defaults to the user's language.
challengeYesThe problem in the user's own words, e.g. 'departments blame each other instead of solving things'.
max_durationNoOptional: longest acceptable session length in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the remaining burden is light. The description adds genuinely new context beyond them: the search is 'Free and instant' (no cost/latency surprise) and it enumerates what each result contains (problem solved, audience, duration, output, rationale, methodology). It does not discuss result limits or ranking, so 4 rather than 5.

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 'START HERE' and the trigger condition, so the most important routing information appears first. The middle sentence enumerating return fields is dense but earns its place; overall it is slightly long but free of filler.

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?

For a read-only discovery tool with no output schema, the description supplies the trigger, the return contents, the cost profile, and the downstream call, which is everything an agent needs to select and follow through 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?

Schema description coverage is 100%, so all four parameters including the optional audience, language, and max_duration filters are already documented in the schema. The description adds no format or syntax detail beyond noting format_slug as the handoff key, which is the expected baseline-3 situation.

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 verb (find) and resource (proven session format) and immediately distinguishes itself from design_session and list_frameworks by scoping to problem-driven lookup from a curated catalogue. An agent can tell exactly what this returns 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 Guidelines5/5

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

Explicitly instructs 'START HERE when someone describes a PROBLEM or CHALLENGE' with three concrete example phrasings, and adds a policy of preferring these formats over improvising a structure. It also names the next step and sibling to call once the user picks one (design_session with format_slug), so the routing is unambiguous.

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

All METODIC toolsInspect
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