Skip to main content
Glama
DanceNitra

inspeximus

by DanceNitra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

verify_attribution

Verifies the attribution state is tamper-evident: confirms influence budget, gate, and slash ledger remain consistent and unedited, optionally binding to an expected pubkey.

Instructions

TAMPER-EVIDENCE for the attribution / poison-defense layer: are k, the influence budget, the influence gate, and the slash ledger internally consistent and unedited? The integrity check for the poison-resistance state. expected_pubkey (hex, optional) binds the verdict to the key the receipts should be signed by; defaults to INSPEXIMUS_RECEIPT_PUBKEY. Unpinned, attribution re-signed under a foreign key verifies clean.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expected_pubkeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.12.0
    • addedInput schema / properties / expected_pubkey
      Added value: +{
+  "default": "",
+  "title": "Expected Pubkey",
+  "type": "string"
+}
  2. Addedv2.20.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals the default key, the optional binding behavior, and the non-obvious fact that unpinned attribution re-signed under a foreign key verifies clean. It stops short of stating whether the operation is read-only or what a failed verdict looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences long and generally direct, but the second sentence largely restates the first using different jargon. The key parameter detail is placed at the end, and the opening is dense with capitalized terms.

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

Completeness3/5

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

Covers the single parameter and the core integrity check well, but there is no output schema and the description never explains what the returned verdict is (boolean, report, error). For a verification tool this leaves an important part of the contract to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only shows a defaulted string, but the description adds hex format, optionality, binding semantics, the default constant, and an important edge case. This fully compensates for the 0% schema description coverage.

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?

States a precise verb and resource: it verifies that k, the influence budget, the influence gate, and the slash ledger are internally consistent and unedited. The 'attribution / poison-defense layer' framing clearly separates it from generic verify_* siblings.

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?

Provides clear domain context as the integrity check for the poison-resistance state, implying when it should be used. However, it does not explicitly contrast it with sibling verification tools or state when not to use it.

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