Skip to main content
Glama

Get capabilities and first steps

autoshort_get_capabilities
Read-onlyIdempotent

Explains the end-to-end AutoShort workflow—drafting, approval, rendering, publishing, automation, and payment—plus required human steps and limits so users know what to do next.

Instructions

Start here. Describes the whole agent workflow end to end — make, approve, render, publish, automate, pay — the only steps a human must do, and the limits. Free.

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": "autoshort_get_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the baseline is met before the description starts. The description adds genuinely non-structured context: that the call is "Free" (no credits consumed) and that it discloses which steps require a human and what the limits are — precisely the information an agent needs before committing to a multi-step flow. It does not describe the response shape, but no output schema exists to lean on.

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?

Roughly twenty words, front-loaded with the imperative "Start here", and every clause carries content: scope, the phases covered, the human-step disclosure, the limits, and the cost signal. Nothing is redundant with the annotations or title.

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 zero-parameter orientation tool with full annotation coverage and no output schema, the description gives enough to know what calling it yields and why it comes first. The only residual gap is that it never says the result is static documentation versus live account state, a small ambiguity in an otherwise complete definition.

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 the baseline of 4 applies; nothing in the schema needs interpretation and the description correctly implies no inputs are required.

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?

"Describes the whole agent workflow end to end" states a specific verb (describes/returns docs) and a specific resource (the capability/workflow overview), and the enumerated phases (make, approve, render, publish, automate, pay) make it clearly distinct from siblings such as get_limits or get_credit_balance. It stops short of saying it returns documentation text rather than live data, which keeps it from a 5.

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

Usage Guidelines4/5

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

"Start here" is an explicit ordering directive that tells the agent to call this before any workflow action, which is strong when-to-use guidance. It does not say when not to use it or acknowledge overlap with get_limits, which also covers limits, so there is no explicit alternatives routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.