Lists session types and wisdom traditions accepted by get_intention, showing what each option sets so you can choose the right session_type and tradition before calling.
List the session types and wisdom traditions get_intention accepts, with what each one sets. Call this to choose a session_type and tradition before calling get_intention. Needs no API key.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses that the tool needs no API key, but does not explicitly confirm read-only/non-destructive behavior, rate limits, or output format. The 'list' verb implies safety, but the disclosure is incomplete.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the purpose, then usage, then a key constraint. Every sentence earns its place and there is no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter discovery tool with no output schema, the description provides everything needed: what it lists, why to call it, when to call it, and that no auth is required. Nothing critical is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so parameter semantics are not applicable. Baseline 4 is appropriate; the description sensibly focuses on what it lists rather than on non-existent inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (List) and resource (session types and wisdom traditions get_intention accepts), and distinguishes itself from the sibling by positioning itself as the prerequisite discovery step. An agent can tell what it 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly instructs to call this tool before get_intention in order to choose a session_type and tradition. The alternative (get_intention) is named and the sequencing is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.