Skip to main content
Glama

Compare Functions

compare_functions
Idempotent

Compares two analyze_function Evidence sets across identity, provider text, calls, references, strings, and normalized CFG topology, citing both sets in every conclusion.

Instructions

Compare two explicit sets of analyze_function Evidence across identity, exact provider text, calls, references, strings, and address-normalized CFG topology. Missing or provider-incompatible facets remain truncated or unknown; every conclusion cites both Evidence sets.

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_functions"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds valuable context: missing or provider-incompatible facets are truncated or unknown, and every conclusion cites both Evidence sets. It does not address why a compare operation is not read-only, but this is not contradictory.

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?

Two sentences with zero waste. The purpose is front-loaded, followed by a concise behavioral note about truncation and citations. Every sentence earns its place.

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 compares complex Evidence objects and has no output schema. The description covers input expectations and facet handling but does not explain the return format—what a 'conclusion' actually looks like or how results are structured. This leaves a significant gap for an agent trying to interpret output.

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 description coverage is 100%, with left and right parameters documented as comparison inputs. The description reinforces that each parameter is an 'explicit set of analyze_function Evidence', but adds no new semantic detail beyond what the schema already provides. Baseline 3 is appropriate.

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 a specific verb (Compare) and resource (two explicit sets of analyze_function Evidence) and lists the dimensions compared. It distinguishes itself from generic compare tools by specifying analyze_function Evidence, though it does not explicitly name sibling alternatives.

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?

Usage is implied from the phrase 'two explicit sets of analyze_function Evidence', indicating when the tool applies. However, there is no explicit guidance on when to use this versus compare_artifacts, compare_application_versions, or other comparison tools, nor are there stated prerequisites or exclusions.

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