Skip to main content
Glama

Create prompt topic

create-prompt-topic

Create an empty prompt topic for one domain and return its id. Topic names are unique per domain, ignoring case.

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": {
      "domain_id": "<domain_id>",
      "name": "<name>"
    },
    "name": "create-prompt-topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTopic name
domain_idYesDomain ID from list-domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain_id / description
      Previous value: -"Domain ID"New value: +"Domain ID from list-domains"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / domain_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a non-destructive write (readOnlyHint=false, destructiveHint=false), so the bar is lower. The description adds a genuine behavioral trait beyond them: names are unique per domain, case-insensitively, which tells the agent a duplicate create will not silently succeed. It doesn't say whether a collision errors or returns the existing topic, which keeps it from a 5.

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

Conciseness5/5

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

Two short sentences with no filler; the return value and the uniqueness constraint are each stated once and up front.

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 two-parameter create tool with no output schema, the description covers inputs, scope, and return value, so an agent has enough to call it. The remaining gap is the duplicate-name outcome, which matters for a uniqueness-constrained create but is left implicit.

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?

Schema coverage is 100%, so both parameters are documented, establishing a baseline of 3. The description adds meaning the schema lacks: 'name' is not just a label but a per-domain case-insensitive unique key, which affects how an agent should generate it.

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

Purpose5/5

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

Specific verb+resource ('Create an empty prompt topic'), states the scope (one domain) and the return value (its id). An agent can distinguish this from create-prompt, update-prompt-topic, and delete-prompt-topic without opening a schema.

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 domain scoping and 'empty' qualifier imply when to reach for this tool, and the schema points to list-domains for the id. But there is no explicit routing versus siblings like update-prompt-topic or create-prompt, and no stated preconditions or failure conditions.

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