Skip to main content
Glama

Ask Scout

ask_scout
Read-onlyIdempotent

Ask Scout, Slipstream's assistant, about cappers and tonight's consensus. Needs a Slipstream Pro account.

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

Input Schema

NameRequiredDescriptionDefault
questionYesThe question, in the person's words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds a genuine behavioral constraint not present in structured data: a Slipstream Pro account is required, which tells the agent about an auth failure mode it would otherwise not anticipate. It does not mention response format or latency, but the auth disclosure is the substantive addition.

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?

Two short sentences with the function front-loaded and the prerequisite second, no filler. The second sentence reads as a bare fragment, which is efficient but slightly abrupt and could have been framed as a precondition cue.

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?

For a one-parameter, read-only assistant tool with rich annotations and no output schema, the definition covers purpose, scope, and the account prerequisite. It stops short of saying what kind of answer comes back (free-text assistant reply rather than structured records), which matters for an agent deciding between this and the structured sibling tools.

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 coverage is 100% and the single parameter is documented as 'The question, in the person's words.' The description adds topic scoping (cappers, consensus) that constrains what should be asked, which is mild value beyond the schema, but nothing about length, phrasing, or multi-part questions. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

Names a specific verb (ask) and a specific resource (Scout, Slipstream's assistant), and scopes the subject matter to cappers and tonight's consensus. It does not distinguish itself from sibling tools like tonights_consensus or capper_open_picks, so an agent cannot tell from the description alone when the assistant is preferable to the direct data tools.

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 only guidance is an implied scope ('about cappers and tonight's consensus') plus an account prerequisite; there is no explicit when-to-use or when-not-to-use versus the direct sibling tools. An agent must infer that this is the natural-language route and the siblings are the structured route.

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