Skip to main content
Glama

Get accepted networks

networks_get
Read-only

Lists the token and network payment pairs the current environment accepts, matching the acceptedPayments list validated by charge creation.

Instructions

List the (token, network) payment pairs this environment accepts right now — the same list charges_create validates acceptedPayments against.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely new behavioral fact — 'right now' signals the list is dynamic and environment-specific, so results should not be cached as static truth — but says nothing about latency, rate limits, or whether the response is an array versus a map.

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?

A single dense sentence with zero filler: the resource definition comes first, the scope qualifier second, and the cross-reference to charges_create last. Every clause carries information an agent can act on.

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?

With no parameters, no output schema, and annotations covering safety, the definition is nearly complete — it names the returned tuple structure (token, network). The only gap is that the container shape of the response (array of objects vs. mapping) is not specified, which matters slightly given the absence of an output schema.

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 there is no parameter semantics to explain; the schema itself is empty and fully consistent with the description. Baseline 4 applies, with no penalty since nothing is left undocumented.

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 specific verb (list) and a precisely scoped resource ((token, network) payment pairs accepted by this environment), including the temporal qualifier 'right now'. It also distinguishes itself from the charges_* family by tying the content to charges_create's acceptedPayments validation, so an agent can place it without opening a schema.

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?

Implies the use case by noting the list is what charges_create validates against, which tells an agent this is reference data to consult before creating a charge. However, it never states when to call it (e.g., before charges_create) or contrasts it with alternatives such as charges_check, leaving the routing inference to the reader.

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