Skip to main content
Glama

compare

Identify metric differences between two completed experiments with matching device, version, action, and conditions.

Instructions

Compare metrics of two completed experiments with matching device, version, action and conditions.

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": {
      "first": "<first>",
      "second": "<second>"
    },
    "name": "compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
firstYes
secondYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 burden and does disclose two meaningful traits: both experiments must be completed, and their device/version/action/conditions must match. It does not state what happens when the precondition fails (error vs empty result), whether the operation is read-only, or how results are returned.

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; every clause (metrics, two, completed, matching attributes) carries information. It is terse rather than padded, though the density leaves the matching constraint slightly compressed.

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?

For a tool with no annotations, no output schema, and two completely undocumented parameters, the description should explain which metrics are compared and what the agent receives back. The precondition is covered, but the result shape and failure behavior are absent, leaving real gaps for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does partially by establishing that 'first' and 'second' are identifiers of completed experiments. It stops short of specifying the identifier format (run ID vs name) or whether order matters for the comparison direction.

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 ('Compare') on a specific resource ('metrics of two completed experiments'), so an agent knows exactly what operation it performs. It does not name or contrast with siblings such as review or get_run, so differentiation is only implied by the word 'compare'.

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 phrase 'two completed experiments with matching device, version, action and conditions' functions as a precondition for use, telling the agent this is not a general-purpose diff. However, it gives no explicit when-not guidance and never points to an alternative when the experiments do not match.

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