Skip to main content
Glama
Sign In

ForAgent

by io.foragent
OverviewDiscussionsAdmin

foragent_doctor

Diagnostics: confirms ForAgent is reachable, you are signed in, and which numbers you own. Its result also carries the full ForAgent guide: how setup, numbers, calls and files work.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The description adds genuinely non-obvious value by disclosing that the result carries the full ForAgent guide, which the agent cannot learn from annotations. However, annotations mark this as non-readOnly and non-idempotent, and the description says nothing about why a diagnostic would not be a pure read, nor about latency or auth failure behavior.

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 compact sentences with the core diagnostic purpose front-loaded and the guide-carrying behavior second. No filler or repetition.

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?

With no output schema, the description must convey what comes back; it covers the three diagnostic signals plus the embedded guide, which is adequate. It could be stronger by saying what a failed check looks like or whether calling it is a prerequisite for other 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?

There are zero parameters, so the baseline of 4 would normally apply, but the description adds no parameter information at all and the schema already carries nothing to interpret. It neither helps nor harms.

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 function: diagnostic verification of reachability, sign-in state, and owned numbers, which is clearly distinct from the action-oriented siblings (call, send, listen). It is clear but does not explicitly contrast itself with those siblings by name.

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?

Usage is only implied: an agent can infer it should run this to verify connectivity or fetch the guide, but there is no explicit 'use this before X' or 'use this instead of Y' guidance. No prerequisites or exclusions are stated.

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

All ForAgent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources