Skip to main content
Glama

Zoya.bg

append_message

Save only explicitly requested user/assistant text; never secrets or sensitive personal data.

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": {
      "session_id": "<session_id>",
      "role": "<role>",
      "content": "<content>"
    },
    "name": "append_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
contentYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It contributes one substantive behavioral rule — a data-safety restriction against persisting secrets or sensitive personal data — but omits that this is a write/persistence operation tied to a session, whether messages are immutable or ordered, and whether any permission or consent (cf. set_memory_consent) is required.

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 short clause pair with the most important constraint (only explicitly requested) front-loaded and no filler. It is efficient, though its brevity edges toward under-specification rather than pure concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, all-required write tool with no annotations and no output schema, the definition leaves session scoping, role values, and persistence/return behavior entirely undocumented. An agent knows the safety rule but not how to fill the arguments correctly or what to expect afterward.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for all three required parameters, so the description must compensate and does not: session_id, role, and content are never explained. "user/assistant text" faintly hints at the role values but does not enumerate them, nor does it say that content is the message body being stored.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb "Save" is present and the resource is narrowed to "user/assistant text", which loosely maps to the name append_message. However, it never states that the text is appended to a conversation/session record, so an agent cannot tell precisely what is persisted or where it lands relative to siblings like get_messages.

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?

"Save only explicitly requested" gives an implicit when-to-use gate, and "never secrets or sensitive personal data" gives a when-not-to-store exclusion. There is no mention of a preferred alternative or of what to do when text is not explicitly requested (e.g., skip the call versus use another tool), so guidance is suggestive rather than decisive.

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