Skip to main content
Glama

connection_check

DestructiveIdempotent

Queues an SSH/Slurm and remote directory check to verify compute and storage access before running simulations.

Instructions

Queue an SSH/Slurm and remote directory check. This does not run a simulation.

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

Input Schema

NameRequiredDescriptionDefault
op_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare openWorldHint, destructiveHint, idempotentHint, and readOnlyHint=false, so the agent knows this is an open-world, potentially destructive, non-read-only operation. The description adds scope by saying it queues an SSH/Slurm and remote-directory check and does not run a simulation, but it does not explain why it is destructive, what may be modified or removed, or what queuing implies operationally.

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 two short, front-loaded sentences with no filler. The primary action is stated first, followed immediately by the most important exclusion.

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

Completeness3/5

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

The tool is simple, has an output schema, and benefits from annotations that cover its safety profile, so the description does not need to explain return values or all side effects. Still, the meaning of the required op_id and the practical usage boundaries are missing, leaving meaningful gaps for an open-world, destructive queuing operation.

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 parameter op_id has no description in the schema and no explanation in the tool description. It is unclear whether op_id identifies an existing queued operation, a newly created operation, or something else, so the description fails to compensate for 0% schema description coverage.

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 uses a specific verb, "Queue," and a specific resource, an SSH/Slurm and remote directory check. It also explicitly excludes simulation execution, which prevents a major misuse, but it does not name a sibling alternative or clearly position itself among the many check_* tools.

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 sentence "This does not run a simulation" provides a useful when-not condition, so an agent can infer this is for connectivity/environment verification rather than simulation execution. However, there is no explicit when-to-use guidance, no prerequisites, and no named alternative for related check tools.

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