Skip to main content
Glama

Compare Managed Members

compare_managed_members
Idempotent

Compare two authenticated managed-member Evidence records by exact signature, declared type, name, and structural shape to classify additions/removals, leaving undecoded matches unknown.

Instructions

Compare two authenticated inspect_managed_members Evidence records using unique-only tiers: exact CIL/signature, exact declared type, name, and raw signature (decoded or not), and decoded structural method shape. Names alone are never a matching basis; a member whose signature was not decoded, or whose same-named counterpart's was not, stays unknown rather than added or removed. Metadata tokens remain build-local coordinates bound to each artifact SHA-256 and MVID, and the tuple digest does not itself remap them.

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

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

A4/5.0
Behavior4/5

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

The description adds substantial behavior beyond the annotations: it specifies unique-only matching tiers, that names alone are never a matching basis, and that undecoded signatures remain unknown rather than being treated as added or removed. It also explains that metadata tokens remain build-local coordinates bound to artifact SHA-256 and MVID, and that the tuple digest does not remap them.

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?

The description is front-loaded with the comparison action and avoids obvious filler. It is dense and jargon-heavy, but each sentence conveys comparison rules, unknown handling, or metadata-binding constraints that matter for correct use.

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 description is rich on comparison semantics and limitations, which suits a complex tool. However, with no output schema, it does not describe the returned comparison result structure or error behavior, leaving an important gap for an agent invoking the tool.

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 description coverage is 100%, so the parameter schema already carries the structural burden. The description still adds meaningful semantics by identifying both inputs as authenticated inspect_managed_members Evidence records rather than arbitrary objects, though it does not separately explain the left/right distinction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: compare two authenticated inspect_managed_members Evidence records. It also enumerates the exact comparison tiers, which distinguishes this from inspection tools and from generic artifact or function comparison siblings.

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 description makes clear that the inputs must be authenticated inspect_managed_members Evidence records, which implies the usage context. However, it does not explicitly say when to choose this over other compare_* siblings, nor does it state exclusions or prerequisites beyond the input type.

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