Skip to main content
Glama
Sign In
Manifold Markets MCP Server

Manifold Markets MCP Server

by bmorphism
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

send_mana

Transfer mana to specified users by providing their user IDs and the amount. Optionally include a message with the transfer.

Instructions

Send mana to other users

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": {
      "toIds": "<toIds>",
      "amount": "<amount>"
    },
    "name": "send_mana"
  }
}

Input Schema

NameRequiredDescriptionDefault
toIdsYesArray of user IDs to send mana to
amountYesAmount of mana to send (min 10)
messageNoOptional message to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose that sending mana reduces the sender's balance, requires authentication, or any error handling. Merely states the basic action.

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?

Single sentence, no wasted words. However, it is underspecified; slightly more detail could improve without losing conciseness.

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?

No output schema and no annotations. Description fails to mention return value, side effects (e.g., balance deduction), or constraints beyond schema. Incomplete for a transactional tool.

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?

Input schema covers 100% of parameters with descriptions. The description adds no additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Description clearly states the action (send) and resource (mana) to other users. It differentiates from sibling tools like add_bounty or award_bounty which have different purposes, though not explicitly.

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?

No guidance on when to use this tool versus alternatives like award_bounty or when not to use it. Missing context on prerequisites or limitations.

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