Skip to main content
Glama

Blame an entity

blame
Read-onlyIdempotent

Show the most recent change to any entity — what changed, when, who, and why. Returns an error if no history exists.

Instructions

Most recent change to an entity — what changed, when, who, why.

Like git blame but for semantic entities (DB columns, functions, env vars, dependencies) and AI agents. If no history exists for the entity, returns {"error": "..."} with protocol-level isError: false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_pathYesExact entity path (no prefix matching). Examples: 'users.email', 'src/auth.py::login', 'env/STRIPE_SECRET_KEY'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
timestampYes
entity_typeYes
entity_pathYes
change_typeYes
diffYes
reasoningYes
agentYes
session_idYes
git_commitYes
projectYes
changeset_idYes
metadataYes
revisit_afterYes
expires_whenYes
errorYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, indicating a safe read operation. The description adds the error behavior ('If no history exists... returns {"error": ...} with isError: false'), providing valuable context beyond annotations.

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 two concise sentences plus an error note, with no wasted words. The first sentence immediately states the purpose, making it front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no nested objects) and the presence of an output schema, the description adequately covers purpose, parameter usage, and special error behavior. It is complete for the context.

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% and the input schema's description of 'entity_path' is detailed with examples and constraints. The tool description does not add additional parameter information, so it meets the baseline but does not exceed it.

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 retrieves the most recent change to an entity, with a helpful 'git blame' analogy. The verb 'blame' and resource 'entity' are specific, and the description distinguishes from siblings by focusing on a single latest change.

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 implies usage through the git blame analogy ('Like git blame but for semantic entities'), but it does not explicitly state when to use this tool versus siblings like 'history' or 'diff'. No exclusions or alternatives are mentioned.

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

Install Server

Other Tools

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/masondelan/selvedge'

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