Skip to main content
Glama

Prepare a sealed-conversation link

prepare_secure_thread_invitation

Use only after the person chose this one lawyer and said yes. Returns a one-use link to the sealed page, valid 15 minutes, only for this person. It sends nothing; the person writes and approves their message on that page. Put no matter details in this call.

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": {
      "attorney_id": "<attorney_id>",
      "person_confirmed": "<person_confirmed>"
    },
    "name": "prepare_secure_thread_invitation"
  }
}

Input Schema

NameRequiredDescriptionDefault
attorney_idYes
person_confirmedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses the link's lifetime (15 minutes), its single-use nature, and that the call sends nothing — the person writes and approves the message on the page. It also warns to put no matter details in the call, which is real behavioral context an agent could not infer from readOnlyHint=false / idempotentHint=false alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the precondition, then the return value, then the side-effect clarification, then the caution. No filler and nothing repeated from the schema or annotations.

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 two-parameter tool with no output schema, the description covers the precondition, what is returned and how long it lives, what does not happen (no message sent), and a data-hygiene constraint. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 meaning, and it largely does: attorney_id is framed as the one lawyer the person chose, and person_confirmed as the person having said yes. It does not restate the UUID format or the const:true constraint, but the semantic intent of both parameters is clear.

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?

The description states a specific verb and artifact: it returns a one-use link to a sealed page, valid 15 minutes, scoped to one person. That is concrete enough to separate it from status/preview siblings like get_secure_thread_status or preview_client_message without opening any schema.

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

Usage Guidelines4/5

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

It gives an explicit precondition: use only after the person chose this one lawyer and said yes. That is a clear when-to-use gate, but it names no alternative tool or when-not condition, so it stops short of full routing guidance.

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