Skip to main content
Glama

Inspect Changes

inspect_changes

Inspect an experiment's changes against its source project, listing created, modified, and deleted files with optional unified diffs.

Instructions

Show what the experiment changed, against the project as it was copied in.

USE THIS before destroying a sandbox, and before telling the developer what you found. It is the evidence for your conclusion.

RETURNS created / modified / deleted file lists plus insertion and deletion counts, and optionally the unified diff. Build output and dependency directories are excluded, so a 30,000-file node_modules will not bury the two lines that matter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_diffNoInclude unified diff bodies, not just statistics.
experiment_idYesThe experiment to inspect.
max_files_with_diffNoCap on files given line-level detail.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
changesNo
deletionsNo
truncatedNo
insertionsNo
experiment_idYes
files_createdNo
files_deletedNo
files_modifiedNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses that build output and dependency directories are excluded, preventing noise. While it does not explicitly say the tool is read-only, the phrasing 'inspect' and 'before destroying a sandbox' strongly implies no side effects.

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?

The description is well-structured with clear sections for purpose, usage, and return values. It is concise yet complete, using formatting like bold headings to highlight key points.

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?

The description covers the output (file lists, counts, optional diff) and mentions exclusions, which is essential for an inspection tool. It lacks details on error handling, but the context and schema provide sufficient information for typical usage.

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?

The schema descriptions for all three parameters are clear and adequate. The description only adds minimal context about the optional diff, which is already implied by the schema's 'include_diff' field.

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 clearly states the tool shows what the experiment changed relative to the original project. It distinguishes itself from siblings by focusing on inspecting changes rather than listing, running, or destroying experiments.

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

Usage Guidelines5/5

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

Explicit guidance is given to use this tool before destroying a sandbox and before reporting findings to the developer. It also states what the tool returns, helping the agent know when to invoke it.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/riyasaxena32/sandbox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server