Skip to main content
Glama

scan_changes

Detect whether code changes add or remove third-party services, personal-data fields, or business-rule numbers before deployment, so you know if terms of service or privacy policy need updating.

Instructions

Call before deploy/release when the user asks whether terms of service or privacy policy need updating. Compares the base branch (merge-base) with the working tree and returns newly added/removed third-party services, personal-data fields, features, and changed business-rule numbers, plus skipped roots and notes on comparison limits; when either is non-empty, "no impact" is not a valid answer. Optional base (branch, tag or commit) overrides the base branch.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scan_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBranch, tag or commit to compare against, e.g. "main" or "v1.4.0". Defaults to the configured baseBranch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/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 substantial work: it explains the comparison basis (merge-base vs working tree), discloses the `skipped` roots and `notes` outputs as comparison limits, and states the interpretive rule that a non-empty skipped/notes makes a 'no impact' answer invalid. It stops short of stating that the tool is read-only with no side effects or whether it needs repo/auth preconditions.

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?

Correctly front-loads the call condition before the mechanics, so an agent reads the trigger first. The middle is a dense enumeration joined by a semicolon that takes a second pass to parse, but no clause is filler.

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?

There is no output schema, and the description compensates by naming the returned categories, the diagnostic fields, and how to interpret them. For a single-parameter scan tool this is nearly everything an agent needs; only the read-only/side-effect profile is left unstated.

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% for the single optional `base` parameter, so the schema already documents branch/tag/commit forms and the configured baseBranch default. The description repeats 'branch, tag or commit' and the override behavior without adding syntax or edge-case detail. Baseline 3 applies when the schema does the lifting.

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?

States a specific verb and comparison ('compares the base branch (merge-base) with the working tree') and enumerates what it returns: added/removed third-party services, personal-data fields, features, and changed business-rule numbers. That is far more precise than a restatement of the name. It never names a sibling tool, so differentiation from scan_data_map or audit is left implicit rather than stated.

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?

Gives an explicit trigger: call before deploy/release when the user asks whether ToS or privacy policy need updating. That is a clear when-to-use condition. It does not say when not to use it or point to an alternative among the sibling tools.

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