Skip to main content
Glama

loop_artifact_verify_or_reuse

Verify completed work with a checker distinct from the maker, or look up reusable artifacts by task and contract.

Instructions

Verify completed work with distinct checker_id != maker_id, or lookup reusable artifact.

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

Input Schema

NameRequiredDescriptionDefault
modeYes
resultNo
task_idNo
maker_idNo
task_hashNo
checker_idNo
contract_digestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a genuinely useful rule — the verifying checker must differ from the maker — but does not say whether verification mutates state, what a passing vs failing verdict looks like, what lookup returns when nothing matches, or whether the operation is idempotent. That is a meaningful gap for a tool that appears to both write verdicts and read artifacts.

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 compact sentence with the verification rule front-loaded and the alternative mode trailing. Nothing is padded, though the density comes at the cost of clarity, and splitting the two modes into separate clauses would have cost little space.

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?

This is a seven-parameter tool with a nested object payload, no annotations, and no output schema — the highest-burden configuration — answered with one sentence. Critical unknowns remain: the shape of result, the role of task_hash vs contract_digest, and what the caller receives back in each mode. Substantially more disclosure is warranted.

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?

Seven parameters with 0% schema description coverage means the description must explain them, and it explains only two: maker_id and checker_id (via the inequality rule). The nested result object, task_id, task_hash, and contract_digest — including the likely binding role of the digest — are entirely undefined anywhere. Enum values for mode are listed in the schema but their behavioral meaning is not elaborated.

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 two concrete operations with their resources: verifying completed work and looking up a reusable artifact. The checker_id != maker_id constraint further sharpens what 'verify' means, making it distinguishable from the task-lifecycle siblings. It loses a point only for folding two distinct capabilities into one terse sentence without saying how they relate.

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 'or' implies the agent picks verify vs lookup, and the mode enum reinforces that split, but the description never states the condition that should select one mode over the other. The separation-of-duties rule (checker_id != maker_id) is the one clear usage constraint offered. No prerequisites, no when-not guidance.

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