Skip to main content
Glama

TANDIU AI infrastructure data

Submit a one-way message to TANDIU (小T)

submit_message
Idempotent

Send a one-way inbound message (commercial inquiry, GPU/compute supply or demand, market signal, or feedback) to TANDIU inbox. Returns technical receipt ACK only (receipt_id); does not answer questions.

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": {
      "content": "<content>"
    },
    "name": "submit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactNoOptional isolated contact info (email/phone/WeChat/Telegram)
contentYesMessage text (max 16KB)
metadataNoOptional structured metadata
client_message_idNoOptional idempotency key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (which already declare readOnlyHint=false and idempotentHint=true), the description adds the key behavioral fact that this is fire-and-forget and the caller receives only a technical receipt_id, not an answer. It does not mention rate limits, delivery latency, or consequences for malformed/oversized payloads, which would be the remaining useful detail.

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?

Two sentences, no waste: the action and accepted categories come first, then the return-behavior caveat. Every clause carries decision-relevant information.

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

Completeness4/5

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

For a simple write tool with full schema coverage and complete annotations, the definition covers action, scope, and return shape (receipt_id), which is what an agent needs to call it correctly. Minor gaps remain around failure modes and whether submissions are ever read or acted on by a human.

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%, so all four parameters including the optional contact, metadata, and client_message_id already carry documentation. The description adds context about what kind of text belongs in 'content' but nothing extra about idempotency-key behavior or metadata structure, so the baseline 3 applies.

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?

States a specific verb and resource ('Send a one-way inbound message ... to TANDIU inbox') and enumerates the accepted message categories (commercial inquiry, GPU/compute supply or demand, market signal, feedback). This clearly separates it from the sibling catalog, which consists entirely of read/query/estimation tools.

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

Usage Guidelines4/5

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

The category list defines when to use it, and 'does not answer questions' is an explicit when-not signal that prevents an agent from treating it as a Q&A channel. It stops short of naming where questions should go instead, so routing for non-submission intents is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources