Skip to main content
Glama
chia-mcp

chia-mcp

Official
by Chia-Network

get_aggsig_additional_data

Read-only

Fetch the per-network AGG_SIG_ME additional data required for BLS signature verification; derived from the genesis challenge, no input parameters needed.

Instructions

Get the AGG_SIG_ME additional data for this network. This is a per-network constant (derived from the genesis challenge) used in BLS signature verification. Takes no parameters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_aggsig_additional_data"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine context beyond that: the returned value is constant per network, it is derived from the genesis challenge, and it serves BLS signature verification — telling an agent the call is deterministic and cheap and what the value is for. It does not state the value's encoding/format, which keeps it off a 5.

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 short sentences: what it returns, what the value is, and the calling contract. Every sentence carries distinct information and the identifying clause is front-loaded.

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 parameterless constant-read tool, the description supplies purpose, provenance, and use case, which is essentially everything an agent needs to decide to call it. The only omission is the shape of the returned value (e.g. hex string vs bytes), which matters slightly since no output schema exists.

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?

With zero parameters the baseline is 4, and the description reinforces it with an explicit 'Takes no parameters', removing any ambiguity about arguments. Nothing further can be added on the parameter side.

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

Purpose4/5

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

States a specific verb (get) and a precise resource (AGG_SIG_ME additional data) and scopes it to 'this network'. The added note that the value is a per-network constant derived from the genesis challenge makes the resource concrete rather than a bare name. It does not need to differentiate from siblings since none of the listed tools overlap, but it also makes no explicit contrast.

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?

'Used in BLS signature verification' implies the context in which an agent would need this value, and 'Takes no parameters' rules out argument planning. However, there is no explicit statement of when to call this versus e.g. get_network_info or a genesis-challenge lookup, so usage is only implied.

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