Skip to main content
Glama

iResolve Private Alignment Rooms

create_alignment_room_link

Read-onlyIdempotent

Returns a privacy-safe HTTPS entry link to start a private solo caucus, 1:1 Sharing Summary bridge, or 3+ anonymous sounding board on iResolve (zero PII stored).

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

Input Schema

NameRequiredDescriptionDefault
localeNo
topologyNo
scenarioSlugNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), and the description adds real value on data handling: 'privacy-safe' and 'zero PII stored'. It says nothing about link expiry, whether the link is single-use, or auth requirements, so the extra context is meaningful but thin.

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 front-loaded sentence that leads with the verb and return value, then the topology options. No filler, though the packed list of three room types makes it slightly dense to parse.

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?

With no output schema, the description correctly explains the return value as an HTTPS link, which is the critical piece. But for a 3-parameter tool with zero schema coverage, leaving scenarioSlug undefined and never referencing the scenario-listing sibling is a real gap.

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 load. It does explain the topology enum by mapping solo/1:1/3+ to concrete room types, but locale and scenarioSlug get no treatment at all, leaving an agent to guess what a scenario slug is and where to find one.

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 and artifact ('Returns a privacy-safe HTTPS entry link') and enumerates the three room topologies it can start, so an agent knows exactly what it gets back. It does not name the sibling list_alignment_scenarios, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied: call this to obtain an entry link for one of three room types. There is no explicit when-to-use vs when-not, and no hint that scenarioSlug likely comes from list_alignment_scenarios, which is the one routing fact an agent would need.

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