Skip to main content
Glama

Blog Submit Draft

tt_blog_submit_draft

STAFF ONLY (allowlisted Tradetron blog staff; everyone else is refused). Create a NEW unpublished DRAFT post on tradetron.tech/blog. It never publishes and never edits an existing post: a blog admin reviews the returned preview_url and publishes from /blog/admin. Check tt_blog_search first so you don't duplicate a topic. body_md: markdown, 300+ words, sections start at ## (never # ). To be publishable it also needs category (a slug from tt_blog_search) and meta_description (50-170 chars). House rules the publish check enforces: call the mode "Live Offline" (the older name is rejected) and never present it as a test (it shows signals; Tradetron places no order); no promised or guaranteed returns ("risk-free", "sure-shot"); FAQ as ## Frequently asked questions + ### Question? headings. The reply's checks.errors lists what must be fixed before publishing. AUTH-REQUIRED.

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": {
      "title": "<title>",
      "body_md": "<body_md>"
    },
    "name": "tt_blog_submit_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
titleYes
body_mdYes
excerptNo
categoryNo
meta_titleNo
meta_descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), but the description adds the real operational context: allowlist enforcement, AUTH-REQUIRED, that the write is a draft that cannot go live, and that the reply carries preview_url and checks.errors. It also enumerates content rules the publish check enforces, which is behavior the agent cannot infer from any structured field.

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 gating and scope statements are front-loaded, which is the right order for a permission-sensitive tool. It is dense with genuinely useful constraints, though the house-rules passage is a single run-on block that could be tightened or bulleted for faster scanning.

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

Completeness5/5

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

There is no output schema, yet the description still tells the agent what comes back (preview_url, checks.errors) and how to act on it. Combined with the permission gate, the draft-only guarantee, and the publishability requirements, an agent has everything needed to call this correctly and interpret the result.

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 0% across 7 parameters, so the description must carry the load. It does well for body_md (markdown, 300+ words, sections start at `## `), category (a slug from tt_blog_search), and meta_description (50-170 chars), but says nothing about slug, excerpt, or meta_title, leaving three parameters undocumented anywhere.

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 uses a specific verb and resource — "Create a NEW unpublished DRAFT post on tradetron.tech/blog" — and immediately rules out the adjacent actions ("never publishes and never edits an existing post"). An agent can distinguish this from a publish or edit tool without inspecting any schema.

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

Usage Guidelines5/5

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

It states the prerequisite audience gate ("STAFF ONLY... everyone else is refused"), the pre-call step ("Check tt_blog_search first so you don't duplicate a topic"), and the downstream path (a blog admin reviews preview_url and publishes from /blog/admin). When-not guidance is explicit: it never publishes and never edits.

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