Skip to main content
Glama
Sign In
Monero MCP Server

Monero MCP Server

by Baltsar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

make_integrated_address

Create an integrated address with a payment ID to identify and track incoming Monero payments.

Instructions

Create an integrated address with a payment ID for identifying incoming payments

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

Input Schema

NameRequiredDescriptionDefault
payment_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states creation of an address but omits details on side effects, permissions, or restrictions (e.g., whether payment ID is required or optional).

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?

The description is a single clear sentence with no wasted words. While very brief, it is front-loaded with the core action. Could be improved with structured bullet points.

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 no output schema and no annotations, the description lacks context on return values, how the integrated address differs from a normal address, and prerequisites. It is incomplete for a tool with these characteristics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description does not explain the payment_id parameter. The phrase 'with a payment ID' is vague; no format, constraints, or usage examples are provided.

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 creates an integrated address with a payment ID for identifying incoming payments. It distinguishes from siblings like create_address by specifying the inclusion of a payment ID.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for payment identification, but lacks when-not or direct references to siblings.

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