Nist Beacon

Chain Info

chain_info

Read-onlyIdempotent

Chain metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	Chain metadata object
`statusCode`	No	HTTP status code

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "chain_id": 1
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "chain": {
+      "description": "Chain metadata object",
+      "type": "object"
+    },
+    "statusCode": {
+      "description": "HTTP status code",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

D1.4/5.0

Behavior2/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the description adds minimal value. However, it fails to disclose any additional behavioral details such as output format or potential limitations.

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

Conciseness2/5

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

Extremely concise (two words), but at the expense of informativeness. The structure lacks any meaningful content; it is under-specified rather than efficiently concise.

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

Completeness2/5

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

Despite having an output schema, the description fails to provide sufficient context about the tool's purpose or input. It is incomplete for a tool that has a required parameter and belongs to a large sibling set.

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

Parameters1/5

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

With 0% schema description coverage, the description must compensate but does not. It offers no explanation of the 'chain_id' parameter's meaning, valid values, or relationship to the output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Chain metadata' is a tautology, restating the tool name without a specific verb or resource. It does not clarify what action the tool performs or what kind of metadata is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance provided on when to use this tool versus its many siblings. The description lacks any contextual hints for selection.

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

All Nist Beacon tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.