nosis-bunker

Official

Overview Schema Source Related Servers Discussions Admin

List supported networks

list_networks

Read-onlyIdempotent

Lists the networks Bunker knows and explains what each exposure model means for interpreting public crypto address checks, with all processing offline.

Instructions

List the networks that Bunker knows, with the meaning of each exposure model. Runs offline.

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": "list_networks"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	No
`models`	No
`networks`	Yes
`attribution`	No
`schemaVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.2Nov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and 'Runs offline' largely restates openWorldHint=false. What the description does add is that the response carries the meaning of each exposure model, giving useful framing about the payload's semantics beyond the structured hints.

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?

Two short sentences with no waste, the resource is front-loaded, and the environment constraint trails as a secondary fact. Every clause carries information.

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 zero-parameter read-only lookup with full annotation coverage and an output schema, the description is nearly sufficient: it states the resource and hints at payload contents. The one minor gap is that 'exposure model' is left undefined, which an agent may not understand without calling the tool.

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?

The tool takes zero parameters, so the schema imposes nothing to explain and the baseline of 4 applies. The description does not need to compensate for any coverage gap and introduces no misleading parameter language.

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?

The description uses a specific verb and resource ('List the networks that Bunker knows') and adds a content hint ('with the meaning of each exposure model'), so its purpose is unambiguous. It does not, however, mention the sibling scan_addresses or explain how a listed network relates to it, so there is no sibling differentiation.

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?

'Runs offline' implies the tool works without connectivity and is therefore safe to call as a reference lookup, which is mild usage guidance. There is no explicit statement of when to prefer this over scan_addresses or any prerequisite/exclusion guidance, leaving selection to inference.

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

Deploy Server