Skip to main content
Glama

TextBot setup help

get_setup_help
Read-onlyIdempotent

Step-by-step help for a setup topic.

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

Input Schema

NameRequiredDescriptionDefault
topicYes

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, idempotentHint, non-destructive, and a closed-world scope, so safety is covered by structured data. The description adds nothing beyond that: it does not say whether the help text is static documentation or dynamically generated, whether results are stable across calls, or what form the steps take.

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?

One short sentence with no filler and the subject is front-loaded. It is not padded, but it is under-specified rather than economical — the brevity comes at the cost of the information an agent needs.

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 simple single-parameter help tool with an enum, the description could plausibly sketch each topic's scope and the shape of the returned steps; it does neither, and there is no output schema to compensate. The definition is callable but leaves the agent guessing about parameter choice and return content.

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%, so the description must carry the burden of explaining the single required parameter and it does not. The enum literals (connect_claude, verify_phone, not_receiving, stop_and_start) are partly self-explanatory but the description never clarifies how to pick a topic or what boundaries exist between them.

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?

"Step-by-step help for a setup topic" names a resource (setup topic) and a content type (step-by-step help), so the agent knows this returns guidance rather than data or actions. However, "setup topic" is left abstract and no sibling is named or implicitly excluded, so distinguishing it from get_text_status or setup_status rests entirely on the reader inferring that help is documentation, not state.

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 when-to-use guidance: nothing says whether this should be called for user confusion, before attempting a setup, or after a failure. No exclusion or alternative is mentioned, so an agent has no rule for choosing this over status-checking tools.

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