Skip to main content
Glama

Sealed message status

get_secure_thread_status
Read-onlyIdempotent

Use when the person gives a status reference (sts_...) from the sealed page. Returns only status words from signed receipts, never content, replies, or whether a consultation happened.

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": {
      "status_reference": "<status_reference>"
    },
    "name": "get_secure_thread_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
status_referenceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description is not needed for safety. It nonetheless adds privacy-relevant context beyond the annotations: results are limited to status words sourced from signed receipts, with no message content, no replies, and no disclosure of whether a consultation occurred.

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?

Two short sentences with the usage trigger front-loaded and the output scope immediately following. Every clause constrains behavior; nothing is filler.

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 one-parameter read tool with no output schema, the description covers trigger, source of the parameter, and the boundary of returned data. It does not hint at what the possible status words are or what happens when receipts are missing, which would have closed the remaining gap.

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?

The single parameter has 0% schema description coverage, so the description must carry the meaning; it explains that the 'sts_...' value is a status reference obtained from the sealed page, clarifying provenance and where the user would have gotten it. It does not restate the allowed character set or length, but the schema pattern already handles that.

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 gives a specific verb and resource: it returns status words from signed receipts for a sealed message thread. Its negative scoping ('never content, replies, or whether a consultation happened') separates it from adjacent messaging siblings, though it does not name an alternative tool explicitly.

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?

'Use when the person gives a status reference (sts_...) from the sealed page' is an explicit trigger condition tied to a recognizable input. There is no stated when-not to use it or named fallback for other lookup cases, so it stops short of the top band.

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