Skip to main content
Glama

list_agent_strategies

Read-only

List AI agent reasoning strategies such as ReAct, hierarchical, and voice, showing how many agents use each plus a breakdown of agents by type (internal, voice, external). Read-only.

Instructions

AI agent reasoning strategies (sn_aia_strategy: ReAct, hierarchical, voice and others) with the number of agents that use each one, and agents by type (internal, voice, external). Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the 'Read-only' sentence is largely redundant restatement. What the description does add beyond annotations is the shape of the result: per-strategy agent counts and a breakdown of agents by type (internal, voice, external), which is genuine behavioral context. It does not address openWorldHint=true (whether the strategy list is fixed or can include custom values) or whether counts are scoped to any tenant or time window.

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?

Two short sentences with no filler, and the resource plus its enumerations are front-loaded. The second clause ('and agents by type (internal, voice, external)') reads as if appended to the first thought, slightly blurring that the response contains two distinct groupings. Still efficient overall.

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 zero-parameter read-only enumeration tool with no output schema, the description does the main job: it identifies the resource, lists the known values, and sketches the return content. The remaining gap is precision about the return structure and whether the counts are tenant-wide or filtered, which matters because no output schema compensates. Given the low complexity of the tool, this is close to sufficient.

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?

The tool takes zero parameters, so the baseline of 4 would normally apply; however, with no input schema surface and no output schema, the description is the only place result semantics could be pinned down, and it only gestures at them. The enumerated strategy values (ReAct, hierarchical, voice) are useful naming context but are not parameters. Scoring at the zero-param baseline would overstate what the description contributes here.

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?

Names a specific resource (AI agent reasoning strategies, tied to the sn_aia_strategy field) and enumerates concrete values (ReAct, hierarchical, voice), plus the aggregation content it returns (agent counts per strategy, agents by type). The implicit verb is 'list', and while the second clause is run-on and mixes two different result sets, an agent can still tell what the tool produces. No sibling is named for differentiation, though the naming pattern against list_agent_* siblings is reasonably self-evident.

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?

There is no statement of when to use this versus alternatives such as list_ai_agents or list_agent_use_cases, and no prerequisites or exclusions. The only usage-adjacent text is the trailing 'Read-only', which describes safety rather than selection context. An agent must infer that this is a discovery/enumeration call from the name alone.

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

Deploy Server

Other Tools