Skip to main content
Glama

Read the message format

get_message_schema
Read-only

Exact fields and length limits for each workbench message kind, named by tool argument, and the domains in use. Read it if a write is refused for its shape, or before choosing a domain.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered elsewhere. The description adds value by characterizing the payload as exact field and length constraints plus currently valid domains, which tells the agent why the tool exists. It does not describe the response's structure or whether the schema is stable across sessions, so it earns only moderate credit beyond the annotations.

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?

Two sentences, front-loaded with the payload and followed by the trigger conditions, with no filler. 'Named by tool argument' is the one clause that costs the reader a second pass; otherwise the wording is dense and purposeful.

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 no output schema present, the description must carry the return-value burden, and it does indicate the substantive contents: per-kind fields, length limits, and valid domains. It could go further by sketching the response shape or whether domains are enumerated exhaustively, but for a zero-parameter read tool it is close to complete.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. The phrase 'each workbench message kind, named by tool argument' does helpfully explain that schema entries are addressed by the corresponding write tool's name, which is meaningful semantics even without parameters.

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 names the resource precisely: exact fields and length limits per workbench message kind, keyed by tool argument, plus the domains in use. That is clearly a meta/schema lookup rather than a data read, which separates it from the get_*/list_* siblings. The only softness is the odd phrasing 'named by tool argument', which leaves the retrieval key slightly implicit.

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 two concrete triggers: read it when a write is refused for its shape, or before choosing a domain. That is real when-to-use guidance tied to an observable failure condition. It stops short of saying when not to bother calling it or naming an alternative source of the same information.

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