Skip to main content
Glama

Can this lawyer receive a sealed conversation?

get_secure_channel_security_state
Read-onlyIdempotent

Use after the person chose one lawyer and asks about a sealed conversation. Returns whether that lawyer can receive one, and warnings. Show every warning in full. The sealed page checks again.

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>"
    },
    "name": "get_secure_channel_security_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
attorney_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds behavior beyond that: the result includes warnings, warnings must be surfaced in full, and the real enforcement happens on the sealed page ('checks again'), telling the agent this is a precheck rather than a guarantee. It omits error behavior for an invalid or unknown attorney_id.

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 usage trigger and followed by the result, the handling instruction, and the caveat. Every sentence earns its place and nothing is padded.

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?

With one required parameter, no output schema, and a full annotation set, the description gives enough to call it correctly and interpret the result: a boolean-style verdict plus warnings that must be shown in full. The lack of any statement about the failure case for an unknown attorney_id is the only meaningful 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 parameter meaning. 'That lawyer' ties attorney_id to the lawyer the person already selected, which is genuine semantic context, and the schema's regex supplies the UUID format. However, it never notes that the ID is required or what happens if a non-matching ID is passed, so it only partly compensates for the coverage gap.

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 states a specific outcome: it returns whether a given lawyer can receive a sealed conversation, plus warnings. The resource and question are unambiguous. It does not explicitly distinguish itself from the similarly named sibling get_secure_thread_status, so it stops short of a 5.

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 a clear trigger condition: use it after the person has chosen one lawyer and asks about a sealed conversation. That is real when-to-use guidance. It stops at 4 because it names no alternative or when-not condition, leaving the agent to infer why the neighboring secure-thread tool is different.

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