Skip to main content
Glama
Sign In
rocketmatter-mcp

rocketmatter-mcp

by RosenAdvertising
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_transaction

Create a bank deposit or withdrawal by providing transaction details in JSON format, including the bank account ID.

Instructions

Create a bank transaction (deposit/withdrawal) via POST /v1/transactions.

fields_json: JSON object with the transaction body (needs a bankId — see list_transactions on bank enumeration). The API's 400 validation names any missing required fields.

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": {
      "fields_json": "<fields_json>"
    },
    "name": "create_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
fields_jsonYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description must fully disclose behavioral traits. It only mentions the API's 400 validation for missing fields, but omits details on permissions, idempotency, side effects, or success/error responses.

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?

The description is very concise, with two sentences that front-load the core purpose and provide essential parameter guidance without extraneous text.

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?

Given the tool simplicity (one parameter, no annotations, output schema exists), the description covers the basics but lacks behavioral context and return value information, leaving gaps for an agent to fully understand the tool's behavior.

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?

The description adds value beyond the empty schema description by stating that fields_json is a JSON object and that it requires a bankId (with a reference to list_transactions). However, it does not enumerate other required or optional fields.

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 clearly states it creates a bank transaction (deposit/withdrawal) via POST /v1/transactions, which distinguishes it from sibling create tools like create_invoice or create_matter. However, it could be more explicit about the specific operation type.

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?

The description provides implicit guidance by mentioning the need for a bankId and referencing list_transactions for enumeration, but lacks explicit when-to-use or when-not-to-use instructions compared to alternatives.

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