Skip to main content
Glama
Sign In
said-done

said-done

by Jimmy2004
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

probe_api

Test the configured API endpoint without sending a model or consuming tokens, so you can verify connectivity before running tasks.

Instructions

Probe the configured endpoint without sending a model or spending tokens.

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

Input Schema

NameRequiredDescriptionDefault
profileNodefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden. It usefully discloses that no model is sent and no tokens are spent, but it does not state whether the probe is read-only, requires authentication, has side effects, or returns success/failure details.

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?

The description is a single front-loaded sentence with no filler or repetition. Its brevity is effective, even though it leaves other gaps unaddressed.

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

Completeness2/5

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

There are no annotations and no output schema, so the description should do more to explain the probe's return behavior, side effects, and the role of the profile parameter. It conveys the core cost-saving behavior but leaves too much undefined for an agent to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional profile parameter has 0% schema description coverage, and the description says nothing about what profile means or how it affects the probe. The default value is visible in the schema, but the description adds no semantic context beyond that.

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 a specific action (probe) and target (the configured endpoint), and clarifies that it avoids sending a model or spending tokens. It distinguishes the tool from token-consuming siblings implicitly, though it does not name an alternative tool or define what probing checks.

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 phrase "without sending a model or spending tokens" implies when to use it: a lightweight endpoint check. However, it gives no explicit when-to-use or when-not-to-use guidance, and does not direct the agent to alternatives such as status or test_classifier.

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

Deploy Server

Other Tools