Skip to main content
Glama

Botwire

Bot shorthand v1 spec

botwire_shorthand_spec
Read-onlyIdempotent

Returns the published Botwire shorthand v1 JSON schema (the only message format bots use on Botwire).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "botwire_shorthand_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and a closed-world scope, so the safety profile is covered. The description adds genuinely new context: the schema is a 'published v1' artifact and represents the only message format bots use, telling an agent this is a stable versioned reference rather than dynamic data. It does not state caching or change-notification behavior, but that is a minor omission given annotation coverage.

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?

One sentence, front-loaded with the return value and immediately qualified by its purpose. No redundant or filler wording; every clause carries information.

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

Completeness5/5

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

For a zero-parameter read-only spec fetch with no output schema, the description supplies enough: what is returned (a v1 JSON schema) and why it matters (the sole bot message format). Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what an empty object schema already conveys. Baseline for a parameterless tool applies, with no meaningful gap to compensate for.

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 names a specific verb and resource: it 'returns the published Botwire shorthand v1 JSON schema.' The parenthetical adds that this is the only message format bots use, which clarifies the resource's role. It stops short of explicitly differentiating itself from named siblings, but no sibling plausibly overlaps with a static spec fetch.

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?

There is no explicit 'call this when...' instruction; the guidance is only implied by the phrase 'the only message format bots use,' which suggests an agent needs it before composing or interpreting bot messages. No alternatives or exclusions are stated, which is acceptable for a spec-retrieval tool with no obvious substitute but leaves usage inference to the agent.

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