Skip to main content
Glama

Compass by 402rates

by com.402rates
OverviewDiscussionsAdmin

Describe a synthetic agent test

describe_agent_test
Read-only

Free description of a versioned synthetic task, its limits and coverage. Optional case selection; omitted selection describes the original confirmation case. No run, payment or wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_idNoVersioned synthetic case identifier.
variantNoBudget case: budget_first or attempts_first. Linked repeats retain the previous variant.
case_versionNoOptional exact case version. A new run defaults to the current published version; a linked repeat retains its previous version. The resolved version is returned and stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / case_version / description
      Previous value: -"Exact case version. No implicit migration."New value: +"Optional exact case version. A new run defaults to the current published version; a linked repeat retains its previous version. The resolved version is returned and stored."
  2. Changed3 schema fields changed
    • addedInput schema / properties / case_id
      Added value: +{
+  "description": "Versioned synthetic case identifier.",
+  "maxLength": 80,
+  "type": "string"
+}
    • addedInput schema / properties / case_version
      Added value: +{
+  "description": "Exact case version. No implicit migration.",
+  "maxLength": 16,
+  "type": "string"
+}
    • addedInput schema / properties / variant
      Added value: +{
+  "description": "Budget case: budget_first or attempts_first. Linked repeats retain the previous variant.",
+  "maxLength": 32,
+  "type": "string"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The read-only, non-destructive profile is already carried by annotations; the description adds value beyond them by disclosing that the call is free of payment/wallet interaction and that omitting case selection defaults to the original confirmation case. No contradiction with annotations.

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?

Three terse sentences, each earning its place: what the tool describes, the default-selection behavior, and the exclusions. The most important job-identifying information is front-loaded with zero fluff.

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-required-parameter read tool with fully documented schema and safety annotations, the description covers purpose, default behavior, and exclusions well. Minor gap: it doesn't describe the shape of the returned description beyond 'limits and coverage,' and there is no output schema to compensate.

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?

Schema coverage is 100%, so the baseline is 3. The description earns an extra point by explaining the omission semantics — selecting no case yields the original confirmation case — which the schema's 'Versioned synthetic case identifier' does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it 'describes' a 'versioned synthetic task, its limits and coverage.' The closing clause 'No run, payment or wallet' explicitly differentiates it from sibling tools like start_agent_test, test_payment, and check_payment_terms, so an agent can pick it without opening the schema.

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?

Gives clear context for the optional-case behavior ('omitted selection describes the original confirmation case') and an explicit when-not signal ('No run, payment or wallet'). However, it never names an alternative tool to use when a run or payment is actually needed, stopping short of full routing.

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

All Compass by 402rates 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