Skip to main content
Glama
Hardik-Singh

Invariance MCP

Official
by Hardik-Singh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

invariance_capture_create

Create a standalone evidence record for a session, conversation, or trace. Capture source, model, tags, and metadata now, then link it to a run later for observability and evaluation.

Instructions

Create a Capture — a standalone evidence record (session, conversation, trace). Captures don't need an execution upfront; link a capture to a run later with invariance_capture_link. Returns the capture session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFree-form labels for filtering and evidence-graph rollups, e.g. ["meeting","q3"]. Normalized (trimmed/lowercased/deduped) server-side.
modelNoModel name used in the session, e.g. "claude-opus-4-7".
titleNoHuman-readable title shown in dashboards.
run_idNoLink this capture to an existing run at creation time. Can also be linked later with invariance_capture_link.
sourceYesOrigin of the capture, e.g. "claude_code", "api", "browser", "zapier".
metadataNoFree-form metadata as a JSON object string. Example: {"user_id":"u_42","environment":"prod"}
capture_typeNoAlias for session_type — use either; session_type takes precedence.
session_typeNoType classification for the session, e.g. "chat", "tool_use", "workflow".
external_session_idNoYour system's session identifier for deduplication and cross-referencing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

It discloses that creating a Capture does not require an execution upfront, that linking can be deferred, and that the tool returns the capture session. This is consistent with annotations readOnlyHint=false and destructiveHint=false, and no contradiction is present.

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?

Three sentences, each with a clear job: define the resource, clarify the deferred-linking behavior, and state the return value. There is no filler or redundant repetition of schema details.

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?

For a create tool with nine documented parameters and no output schema, the description provides adequate orientation: it defines what a Capture is, explains the relationship to run linking, and states the return type. It could more explicitly differentiate Capture from related session/case creation tools, but the essential invocation context is present.

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 description coverage is 100%, so the structured schema already documents all parameters thoroughly. The description adds context about deferred linking via invariance_capture_link but does not materially expand the meaning of individual parameters beyond what the schema already provides.

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 opens with a specific verb-resource pair ('Create a Capture') and defines the resource as a 'standalone evidence record (session, conversation, trace)'. The deferred-linking behavior ('link a capture to a run later with invariance_capture_link') clearly distinguishes this tool from run-creation and capture-linking siblings.

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 communicates the key usage context: captures are for standalone evidence that can be linked to a run later, naming invariance_capture_link as the follow-up tool. It does not explicitly enumerate when-not-to-use cases or contrast with sibling tools like session_create, but the intended workflow is clear.

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