Skip to main content
Glama

environment_verify

DestructiveIdempotent

Verifies a completed environment_check run against collected engine output and an expected scientific marker to confirm environment readiness.

Instructions

Verify a completed environment_check run using collected engine output and a scientific verification marker.

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": {
      "run_id": "<run_id>",
      "evidence_path": "<evidence_path>",
      "expected_text": "<expected_text>",
      "op_id": "<op_id>"
    },
    "name": "environment_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
run_idYes
evidence_pathYes
expected_textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=true, which is surprising for something called 'verify', yet the description never says what is mutated or destroyed, nor that the operation is idempotent (idempotentHint=true). With a destructive mutation wrapped in read-sounding language, the description carries a burden it does not meet — though it does not explicitly contradict the annotations.

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?

A single front-loaded sentence with no filler; the subject and action lead. It is efficient, if only because it omits rather than compressing detail.

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?

An output schema exists so return values need no explanation, but with four undocumented required parameters and an undisclosed destructive side effect on a verification-style tool, the definition is not complete enough for safe invocation.

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?

There are four required parameters at 0% schema description coverage, so the schema supplies no semantics at all. The description only adumbrates 'engine output' and a 'verification marker' and never explains run_id, evidence_path, expected_text, or op_id, leaving the agent to guess at formats and expectations.

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 verb ('Verify') and a specific target ('a completed environment_check run'), and adds that the check uses collected engine output plus a scientific verification marker. An agent can tell this acts on a finished check rather than on raw capture, though it never explicitly contrasts itself with environment_capture.

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?

'Completed environment_check run' implies a sequencing precondition: a prior check must have finished before this runs. There is no statement of when not to use it, no mention of an alternative tool, and no note on what to do if the check failed or is still running.

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