Skip to main content
Glama

Inspect

sandbase_inspect
Read-only

Inspect a model, API, or Agent Service: input schema, available pricing, and an execution template. Service names are svc_ IDs. Always inspect before running.

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

Input Schema

NameRequiredDescriptionDefault
nameYesModel name (e.g. 'openai/gpt-4o'), tool name, or Agent Service ID (svc_...) from discover results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so safety is covered; the description adds the payoff that the call returns schema, pricing, and an execution template, which is the key behavioral fact given there is no output schema. It does not discuss caching, failure modes for unknown names, or idempotency, leaving modest gaps.

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?

Two sentences, front-loaded with the core action and its outputs, then the imperative prerequisite. No filler, no restatement of the 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 one-parameter read-only tool this is nearly complete: it names what the call returns, which compensates for the absent output schema, and states the required ordering relative to run. The only omission is how the returned execution template should be used downstream.

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?

The single parameter is fully documented in the schema (model name, tool name, or svc_ ID from discover results), so the schema does the heavy lifting. The description repeats the svc_ ID convention for services and adds 'model, API, or Agent Service' as the accepted name space, but contributes little beyond what the schema already states.

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?

States a specific verb (inspect) over a specific resource set (model, API, Agent Service) and enumerates what the inspection yields: input schema, pricing, and an execution template. This reads clearly against discover/run siblings without naming them, though it stops short of an explicit 'not the same as sandbase_discover' contrast.

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?

'Always inspect before running' gives an explicit sequencing rule that ties this tool to sandbase_run as a prerequisite, which is exactly the guidance an agent needs. It omits any when-not condition (e.g., for already-inspected names or cache hits), so it is clear context rather than a full decision matrix.

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.