Skip to main content
Glama

Create topic

create_topic
Destructive

Create a subscription topic, so people can opt out of one kind of message (e.g. promotions) and keep others.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTopic name
descriptionNoWhat the topic covers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"What the topic covers"
    • addedInput schema / properties / name / description
      Added value: +"Topic name"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, so the safety profile is covered. The description adds nothing about duplicate-name behavior, whether creation is reversible, or what the caller gets back — useful context that annotations cannot supply. Adequate but not rich.

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 well-formed sentence that front-loads the action and uses the remainder for the one piece of conceptual context worth knowing. No redundancy, though the parenthetical example is slightly verbose.

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

Completeness3/5

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

With only two simple parameters, no nested objects, and no output schema, little is required — but for a non-idempotent destructive create, the description leaves the agent without knowledge of duplicate handling or the returned object. Just enough to call it, not enough to call it confidently.

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 description coverage is 100%, so both parameters (name, description) are already fully documented with types and max lengths. The description adds no additional semantics such as naming conventions or uniqueness expectations, so the baseline 3 applies.

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?

States a specific verb and resource (create a subscription topic) and adds a clarifying gloss on what a topic is: a per-message-category opt-out channel. This meaningfully separates it from create_list and create_segment, though it does not name those siblings 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?

The clause about letting people opt out of one kind of message implies the use case, but there is no explicit when-to-use guidance, no mention of create_segment/create_list as alternatives, and no note that update_topic exists for modifying an existing topic.

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.