Skip to main content
Glama

Find Changed Behavior

find_changed_behavior
Idempotent

Aggregates validated process and artifact comparison evidence to identify changed behavior, separating runtime observations from static candidates and marking incomplete comparisons unresolved.

Instructions

Aggregate validated process and artifact comparison Evidence. Runtime observations remain distinct from static behavior candidates; missing or incomplete comparisons produce unresolved findings, never causal claims. Returns every finding 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": {
      "comparisons": "<comparisons>"
    },
    "name": "find_changed_behavior"
  }
}

Input Schema

NameRequiredDescriptionDefault
comparisonsYesValidated comparison Evidence records to aggregate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety hints, but the description adds meaningful behavioral context: it distinguishes runtime observations from static behavior candidates, explains that incomplete comparisons yield unresolved findings rather than causal claims, and states that every finding is returned inline. It still does not explain the practical implication of readOnlyHint=false for an aggregation operation or describe any permission or computation constraints.

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 compact and front-loads the core action before stating epistemic limits and return behavior. Each sentence contributes, though the phrasing is dense and could be made slightly more explicit without losing concision.

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 accepts a complex array of Evidence records and has no output schema, so the description must carry more burden. It states that findings are returned inline but does not describe the finding structure, aggregation rules, deduplication, or how changed behavior is determined.

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 100%, so the input schema already documents the sole 'comparisons' parameter. The description echoes the idea of aggregating comparison Evidence but does not add format, ordering, or validation details beyond the schema.

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 and resource: 'Aggregate validated process and artifact comparison Evidence.' It clarifies that runtime observations and static behavior candidates remain distinct, but it does not explicitly differentiate this aggregation step from sibling comparison tools such as compare_functions or compare_artifacts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives semantic rules, such as missing comparisons producing unresolved findings, but never states when an agent should call this tool instead of the many compare_* siblings or other discovery tools. It implies use after comparisons exist, but does not make the selection criteria explicit.

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