Selvedge

Overview Schema Source Related Servers Discussions Admin

Blame an entity

blame

Read-onlyIdempotent

Trace the most recent change to any code entity, including who, when, why, and whether it is active, reverted, or superseded, to understand its provenance.

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. Also carries the derived decision state: status (active / reverted / reopened) and superseded_by (id of a later supersede overriding this change, or ""). If no history exists for the entity, returns {"error": "..."} with protocol-level isError: false.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`entity_path`	Yes	Exact entity path (no prefix matching). Examples: 'users.email', 'src/auth.py::login', 'env/STRIPE_SECRET_KEY'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`diff`	Yes
`agent`	Yes
`error`	Yes
`status`	Yes
`project`	Yes
`metadata`	Yes
`reasoning`	Yes
`timestamp`	Yes
`constraint`	Yes
`git_commit`	Yes
`session_id`	Yes
`stale_when`	Yes
`supersedes`	Yes
`change_type`	Yes
`entity_path`	Yes
`entity_type`	Yes
`changeset_id`	Yes
`expires_when`	Yes
`revisit_after`	Yes
`superseded_by`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.3.10Jul 13, 2026

addedOutput schema / properties / constraint

Added value: +{
+  "title": "Constraint",
+  "type": "string"
+}

addedOutput schema / properties / stale_when

Added value: +{
+  "title": "Stale When",
+  "type": "string"
+}

addedOutput schema / properties / status

Added value: +{
+  "title": "Status",
+  "type": "string"
+}

addedOutput schema / properties / superseded_by

Added value: +{
+  "title": "Superseded By",
+  "type": "string"
+}

addedOutput schema / properties / supersedes

Added value: +{
+  "title": "Supersedes",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "timestamp",
-  "entity_type",
-  "entity_path",
-  "change_type",
-  "diff",
-  "reasoning",
-  "agent",
-  "session_id",
-  "git_commit",
-  "project",
-  "changeset_id",
-  "metadata",
-  "revisit_after",
-  "expires_when",
-  "error"
-]New value: +[
+  "id",
+  "timestamp",
+  "entity_type",
+  "entity_path",
+  "change_type",
+  "diff",
+  "reasoning",
+  "agent",
+  "session_id",
+  "git_commit",
+  "project",
+  "changeset_id",
+  "metadata",
+  "revisit_after",
+  "expires_when",
+  "supersedes",
+  "constraint",
+  "stale_when",
+  "superseded_by",
+  "status",
+  "error"
+]

Changed3 schema fields changedv0.3.8Jun 17, 2026

addedOutput schema / properties / expires_when

Added value: +{
+  "title": "Expires When",
+  "type": "string"
+}

addedOutput schema / properties / revisit_after

Added value: +{
+  "title": "Revisit After",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "timestamp",
-  "entity_type",
-  "entity_path",
-  "change_type",
-  "diff",
-  "reasoning",
-  "agent",
-  "session_id",
-  "git_commit",
-  "project",
-  "changeset_id",
-  "metadata",
-  "error"
-]New value: +[
+  "id",
+  "timestamp",
+  "entity_type",
+  "entity_path",
+  "change_type",
+  "diff",
+  "reasoning",
+  "agent",
+  "session_id",
+  "git_commit",
+  "project",
+  "changeset_id",
+  "metadata",
+  "revisit_after",
+  "expires_when",
+  "error"
+]

Changed2 schema fields changedv0.3.2May 3, 2026

addedInput schema / properties / entity_path / description

Added value: +"Exact entity path (no prefix matching). Examples: 'users.email', 'src/auth.py::login', 'env/STRIPE_SECRET_KEY'."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "agent": {
+      "title": "Agent",
+      "type": "string"
+    },
+    "change_type": {
+      "title": "Change Type",
+      "type": "string"
+    },
+    "changeset_id": {
+      "title": "Changeset Id",
+      "type": "string"
+    },
+    "diff": {
+      "title": "Diff",
+      "type": "string"
+    },
+    "entity_path": {
+      "title": "Entity Path",
+      "type": "string"
+    },
+    "entity_type": {
+      "title": "Entity Type",
+      "type": "string"
+    },
+    "error": {
+      "title": "Error",
+      "type": "string"
+    },
+    "git_commit": {
+      "title": "Git Commit",
+      "type": "string"
+    },
+    "id": {
+      "title": "Id",
+      "type": "string"
+    },
+    "metadata": {
+      "additionalProperties": true,
+      "title": "Metadata",
+      "type": "object"
+    },
+    "project": {
+      "title": "Project",
+      "type": "string"
+    },
+    "reasoning": {
+      "title": "Reasoning",
+      "type": "string"
+    },
+    "session_id": {
+      "title": "Session Id",
+      "type": "string"
+    },
+    "timestamp": {
+      "title": "Timestamp",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "timestamp",
+    "entity_type",
+    "entity_path",
+    "change_type",
+    "diff",
+    "reasoning",
+    "agent",
+    "session_id",
+    "git_commit",
+    "project",
+    "changeset_id",
+    "metadata",
+    "error"
+  ],
+  "title": "BlameResult",
+  "type": "object"
+}

First observedv0.3.1Apr 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate safe read-only idempotent operation. The description adds value by detailing return fields (status, superseded_by) and error handling behavior (returns error object with isError: false). No contradiction.

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?

Two short paragraphs, no fluff. The first sentence immediately states the core purpose. Every sentence adds necessary context.

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 a single parameter, existing output schema, and comprehensive annotations, the description covers the tool's functionality, return data, and error case fully and clearly.

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?

Only one parameter with 100% schema coverage. The description adds the constraint 'exact entity path (no prefix matching)' and provides examples, enhancing the schema's description.

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, likening it to git blame for semantic entities. It distinguishes from siblings like history or diff by focusing on the latest change and including decision state.

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?

The description explains what the tool does and notes error behavior when no history exists. It lacks explicit guidance on when not to use or alternatives, but the purpose is clear enough for correct selection.

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

Deploy Server