Skip to main content
Glama

iResolve Private Alignment Rooms

list_alignment_scenarios

Read-onlyIdempotent

Lists public iResolve private-caucus and double-blind summary alignment scenarios across English and French (zero PII, 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_alignment_scenarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description does add two traits beyond that structure: results are public-only and contain zero PII, which matters for an agent deciding whether output is safe to surface. It says nothing about result volume, pagination, or what a "scenario" record contains (no output schema exists).

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?

A single dense sentence with the key scope and safety facts front-loaded and no filler. It is slightly jargon-heavy ("iResolve", "private-caucus", "double-blind summary alignment scenarios") for a reader unfamiliar with the domain, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with no output schema, the definition covers scope, safety, and locale, which is close to sufficient. The remaining gap is what the returned scenarios look like and whether results are paged or bounded, which the agent needs to plan its call.

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 0%, so the description must carry the single locale parameter, and it does partially by naming English and French. However, "across English and French" reads as though both languages are always returned, leaving it ambiguous whether locale selects one language or the phrase merely describes coverage, and no default is stated for this optional parameter.

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?

The description opens with a specific verb and resource ("Lists ... alignment scenarios") and narrows scope with concrete qualifiers: public, iResolve, private-caucus and double-blind summary variants. An agent can distinguish it from the write-oriented sibling create_alignment_room_link on verb alone, though no explicit sibling contrast is stated.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. Usage is only inferable from the word "Lists" and the word "public" implying a catalog-browsing operation rather than a filtered query.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources