Skip to main content
Glama
r3e-network

Neo N3 MCP Server

by r3e-network
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

invoke_contract

Invoke a read-only method on a Neo N3 smart contract to retrieve data without transaction fees or signing.

Instructions

Run a read-only smart contract invocation without signing or broadcasting a transaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoMethod arguments as an array of values
networkNoNetwork to query
contractNoContract reference: script hash, Neo address, exact N3Index name, or a previously discovered manifest name
operationYesContract method name to invoke
nameOrHashNoContract name or script hash (alias for contract)
scriptHashNoContract script hash (40 hex chars, optional 0x prefix)
contractNameNoExact contract name resolved through N3Index or a live manifest

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv3.1.0
    • removedInput schema / properties / confirm
      Removed value: -{
-  "description": "Set to true to execute write operations (safety confirmation)",
-  "type": "boolean"
-}
    • changedInput schema / properties / contract / description
      Previous value: -"Contract reference: known name (e.g. \"NeoFS\"), script hash (0x...), or Neo address"New value: +"Contract reference: script hash, Neo address, exact N3Index name, or a previously discovered manifest name"
    • changedInput schema / properties / contractName / description
      Previous value: -"Known contract name (e.g. \"GAS\", \"NEO\", \"NeoFS\")"New value: +"Exact contract name resolved through N3Index or a live manifest"
    • removedInput schema / properties / fromWIF
      Removed value: -{
-  "description": "Sender WIF private key (required for write operations)",
-  "type": "string"
-}
    • changedInput schema / properties / network / description
      Previous value: -"Network to use: mainnet or testnet"New value: +"Network to query"
    • addedInput schema / properties / network / enum
      Added value: +[
+  "mainnet",
+  "testnet"
+]
    • removedInput schema / properties / signers
      Removed value: -{
-  "description": "Transaction signer scopes for write operations",
-  "items": {},
-  "type": "array"
-}
  2. Addedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

The description states it is read-only and non-broadcasting, clarifying it is non-destructive. However, with no annotations provided, it fails to disclose other behavioral aspects like error handling, result structure, or limits. The read-only trait is the key behavioral detail, earning a 3.

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 concise sentence conveys the core purpose with no redundancy. However, it could be slightly more structured (e.g., separate lines for key details) without losing brevity.

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?

Given the complexity of 7 parameters and no output schema, the description is too minimal. It does not explain how to use multiple contract identifiers, expected output format, or error conditions. For a tool of this complexity, more context is needed.

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 coverage is 100%, so the descriptions in the schema already document all parameters. The tool description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool's purpose: performing a read-only contract invocation without signing or broadcasting. This precisely distinguishes it from other tools like estimate_invoke_fees or get_contract_info.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it explain which parameter among the multiple contract identifiers (contract, nameOrHash, scriptHash, contractName) should be used in different scenarios. Required parameter 'operation' is mentioned in schema but not in description context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/r3e-network/neo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server