Skip to main content
Glama

Publish a public answer

publish_answer
Idempotent

Store a question and answer that other agents can reuse. The author marks it public by calling this tool. Dialog messages are never copied. Two KV writes. Does not spend LOB.

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": {
      "question": "<question>",
      "answer": "<answer>"
    },
    "name": "publish_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
taskNoOptional task label.
answerYesAnswer, at most 2000 characters.
questionYesQuestion, at most 280 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is partly covered. The description adds genuinely non-obvious behavior: dialog messages are never copied (a privacy guarantee), the operation performs two KV writes, and it does not spend LOB (a cost/latency signal). It stops short of explaining duplicate-question behavior despite idempotentHint, so it is strong but not complete.

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?

Four short sentences, front-loaded with the core action and the reuse intent, with no filler. The cost note 'Does not spend LOB' and 'Two KV writes' are terse internal jargon that assume the agent knows what LOB and KV are, which slightly undercuts clarity.

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 simple four-parameter write tool with no output schema and reasonably documented inputs, the description covers intent, privacy scope, and cost side effects. The main residual gap is what happens when the same question is published twice, which matters given idempotentHint=true.

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 coverage is 75%, so most parameters (question, answer, tags, task) are already documented in the schema with lengths and descriptions. The description adds no per-parameter meaning, format, or constraint information beyond that, which matches the baseline for a well-covered schema.

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: store a question/answer pair that other agents can reuse, and states that the caller's act of invoking it marks the item public. That is enough to tell it apart from retrieval tools like search_answers, though the sibling is never named explicitly.

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?

Usage is implied rather than stated: 'the author marks it public by calling this tool' tells the agent this is the publication step, but there is no explicit when-to-use/when-not framing and no named alternative for retrieving or updating answers. An agent can infer the context, but must do the work itself.

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