Skip to main content
Glama

multicall

Read-onlyIdempotent

Batch multiple read-only smart contract calls into one request to reduce round trips and retrieve TRON blockchain data.

Instructions

Execute multiple read-only functions in a single batch call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calls": "<calls>"
    },
    "name": "multicall"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYesArray of calls to execute
networkNoNetwork name. Defaults to mainnet.
versionNoMulticall version (2 or 3). Defaults to 3.
allowFailureNoWhether to allow individual calls to fail. Defaults to true.
multicallAddressNoOptional Multicall contract address override

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / calls / items / additionalProperties
      Removed value: -false
    • addedInput schema / properties / calls / items / properties / abi / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / calls / items / properties / args / items / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "items": {
      -      "type": "number"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "additionalProperties": {},
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "items": {
      +      "type": "number"
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  }
      +]
  2. First observedv1.1.7

TDQS

B3.2/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=true, so the safety profile is covered elsewhere. The description does add one meaningful constraint beyond that: the batched functions themselves must be read-only. It says nothing about atomicity, partial failure handling (despite an allowFailure parameter), or what comes back from the batch.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or repetition. It is tight, though the brevity is close to under-specification for a five-parameter batched tool.

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

Completeness3/5

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

Parameters are fully covered by the schema and the safety profile by annotations, so the definition is callable. However, for a nested batch-execution tool with no output schema, the description omits how results or per-call failures are returned, which is exactly the information the schema cannot supply.

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 description coverage is 100%; every parameter, including nested calls fields and defaults for network, version, allowFailure and multicallAddress, is documented in the schema. The description adds no parameter-level meaning beyond "multiple", so baseline 3 applies.

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 concrete verb ("Execute") and resource ("multiple read-only functions") with explicit scope ("in a single batch call"), so an agent knows this is a batched read tool. It does not name or contrast any sibling tool, so differentation is left to the agent, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use exclusions, and no alternative named. The phrase "multiple ... in a single batch" weakly implies the batching use case, but nothing tells the agent when to prefer this over issuing individual read calls.

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

Deploy Server

Other Tools