Skip to main content
Glama

Compare Artifacts

compare_artifacts
Idempotent

Compares complete artifact inventories by logical path, content identity, metadata, and graph relations, citing every delta and flagging gaps as truncated or unknown instead of equivalence.

Instructions

Compare complete artifact inventories by logical occurrence path, content identity, metadata, and graph relations. Pass the inventory Evidence nested in each inspect_artifact result as left and right. Every delta cites both inputs, and gaps yield truncated or unknown, never equivalence. Returns every change inline.

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": {
      "left": "<left>",
      "right": "<right>"
    },
    "name": "compare_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftYesLeft-hand input used for comparison or differential execution.
rightYesRight-hand input used for comparison or differential execution.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Adds real behavior beyond the annotations: every delta cites both inputs, gaps degrade to truncated/unknown rather than being treated as equivalence, and results come back inline without paging. Annotations already cover the safety profile (non-destructive, idempotent, closed-world), so the remaining gaps are minor; note readOnlyHint=false is not contradicted since the description never claims a pure read.

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?

Four tight sentences with no filler; the comparison scope leads, the input-provenance rule follows, and the semantic caveat about gaps and inline results closes it out. Dense terminology is unavoidable here but nothing is redundant.

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?

With a deeply nested Evidence schema and no output schema, the description covers the two things an agent most needs: where the inputs come from and how results are shaped (inline, every change, no silent equivalence). It could say more about size limits or whether unmatched inputs are an error, but the essentials are present.

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% and both parameters are documented generically as left/right comparison inputs, so the schema already does the baseline work. The description earns credit by constraining what qualifies: the Evidence must be a complete artifact inventory produced by inspect_artifact, which the schema does not say.

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?

Specific verb plus resource ("Compare complete artifact inventories") and it enumerates the comparison axes: logical occurrence path, content identity, metadata, graph relations. That distinguishes it from generic siblings like compare_bundles or compare_functions, though it never names an alternative explicitly.

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?

It gives a concrete precondition for invocation: pass the inventory Evidence nested in each inspect_artifact result as left and right. That tells the agent both how to obtain inputs and which tool feeds this one, but there is no statement of when to prefer this over the other compare_* tools.

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

Deploy Server

Other Tools