creedspace-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_scale_attestation

Read-only

Retrieve an attestation record with its hash chain for a specified entity and scale level (micro, meso, or macro) to verify integrity and provenance.

Instructions

Get attestation record with hash chain for a specific scale and entity

Input Schema

TableJSON Schema

Name	Required	Description
`scale`	Yes	Scale level for attestation
`entity_id`	Yes	Entity ID to get attestation for
`include_chain`	No	Include parent hash chain

Output Schema

TableJSON Schema

Name	Required	Description
`chain`	No	Parent hash chain; present when include_chain was set
`scale`	No	Alignment scale of the attestation
`entity_id`	No	Entity the attestation belongs to
`attestation`	No	Null when no attestation exists for the entity

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.1.4Sep 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Attestation record, attestation chain, or null-attestation placeholder",
+  "properties": {
+    "attestation": {
+      "description": "Null when no attestation exists for the entity",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "chain": {
+      "description": "Parent hash chain; present when include_chain was set",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "entity_id": {
+      "description": "Entity the attestation belongs to",
+      "type": "string"
+    },
+    "scale": {
+      "description": "Alignment scale of the attestation",
+      "type": "string"
+    }
+  },
+  "required": [],
+  "type": "object"
+}

First observedv1.1.3Jul 11, 2026

TDQS

A4/5.0

Behavior4/5

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

The description mentions the hash chain inclusion, adding useful info about the response. With readOnlyHint true, there is no contradiction and no hidden 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?

Single concise sentence that immediately conveys the tool's core purpose without unnecessary detail.

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 is sufficient for understanding the tool's function given the output schema exists. It doesn't need to elaborate on return format, but the mention of hash chain provides 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 descriptions cover the parameters adequately. The description adds minimal extra meaning beyond restating 'scale and entity', so baseline of 3 is appropriate.

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 action (get), the resource (attestation record), and specific scoping (by scale and entity). It is distinct from sibling tools like 'attest_response' and 'get_anchor'.

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 for retrieving attestation records by scale and entity, but does not explicitly mention when to choose this over alternatives or provide any usage conditions.

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

Deploy Server