Skip to main content
Glama

askround_doctor

Verifies which AI providers can run by checking each required key variable without reading its value, plus model and search tool, then making a free test call to each.

Instructions

Which providers can run here: the key variable each reads (never its value), the model and the search tool. Makes a free check call to each.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose meaningful behavior: it reads only key variable names and never their values (a security-relevant guarantee), and it performs a live 'free check call to each' provider, telling the agent this touches the network at no cost. It stops short of saying whether the tool errors out, how latency scales with provider count, or the exact response shape.

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 core answer (which providers work) front-loaded and the safety caveat ('never its value') attached directly to the relevant item. The colon-fragment opening is slightly unpolished but wastes no space.

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 diagnostic with no output schema and no annotations, the description covers what is inspected and roughly what comes back (providers, key variable, model, search tool). Only the failure/empty-config case is unaddressed, which is a minor gap at this complexity level.

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; the baseline for a parameterless tool applies. The description correctly implies a no-argument invocation.

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 states concretely what the tool reports: which providers are runnable, the key variable each reads (explicitly not its value), the model, and the search tool. That is specific enough to distinguish it from siblings like askround_ask or askround_run, which perform work rather than diagnose configuration, though the phrasing is a sentence fragment rather than a verb-led statement.

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 guidance on when to call this versus alternatives, nor on prerequisites or outcomes (e.g., what happens when a provider is unconfigured). The only implicit cue is 'makes a free check call to each,' which hints it is cheap enough to run liberally, but usage context is left to inference.

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