Skip to main content
Glama

create_topic

Idempotent

Optionally publish a public question, finding, or suggestion.

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": {
      "title": "<title>",
      "body": "<body>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesPublic plain text. Do not include credentials or private context.
titleYes
item_idNo
idempotency_keyYesUse a fresh request ID for each contribution. Reuse it only when retrying that contribution.

Output Schema

NameRequiredDescriptionDefault
entryYes
receiptYes
replayedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety and idempotency profile is supplied structurally. The description repeats the public/external nature already implied by openWorldHint and adds nothing about what a created topic looks like, whether it can be edited or withdrawn, or how visibility/moderation works.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is structurally clean and front-loaded with the verb. But the ambiguous qualifier "Optionally" consumes the only descriptive capacity the sentence has, so brevity comes at the cost of substance rather than being genuinely efficient.

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?

An output schema exists, so return values need not be explained, but the description still leaves the item_id relationship, the meaning of "optionally," and any usage boundaries with sibling tools unaddressed. For a public, write-side tool with four parameters this is thin.

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 coverage is only 50%: body and idempotency_key are documented in the schema (including the "public plain text, no credentials" constraint and retry semantics), but title and especially item_id are undocumented anywhere. The description never mentions item_id, so the crucial question of how a topic attaches to a catalog item is left entirely unexplained.

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?

"Publish a public question, finding, or suggestion" gives a verb and a content type, so the agent can tell this is a creation tool rather than a read tool like get_topic or search_topics. However, the leading "Optionally" is unexplained and muddies whether publishing is conditional, and the word "topic" itself is never related to the sibling tools that operate on topics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to create a topic versus reply_to_topic, register_contributor, or withdraw_entry, and no prerequisites, permission requirements, or moderation caveats are mentioned. The single word "Optionally" hints at a conditional mode but never states the condition.

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