3dBlock Studio

Overview Schema Source Related Servers Discussions Admin

post_kit

Creates a posting bundle beside each take with caption, up to five hashtags, song note, and posting time while keeping guessing-format answers out of the caption.

Instructions

Write the post kit next to the takes: caption, up to 5 hashtags, song note, posting time. The answer of a guessing format is kept out of the caption.

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": {
      "slug": "<slug>"
    },
    "name": "post_kit"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	episode slug, e.g. the-cursed-tape (or an example slug for read-only tools)
`song`	No
`caption`	No
`hashtags`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

C2.7/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 the full behavioral burden. It says "Write", implying a mutation, but does not disclose whether an existing post kit is overwritten, what permissions are needed, or what is returned. The rule about keeping a guessing-format answer out of the caption is useful domain behavior but does not compensate for the missing mutation semantics.

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 two short sentences with no obvious filler, and the main action is front-loaded. The second sentence is somewhat awkwardly phrased but appears to encode a real domain rule rather than repetition.

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?

For a mutation tool with no annotations, no output schema, and only partial schema description coverage, the description is too thin. It omits overwrite behavior, required permissions, return value expectations, and leaves a mentioned field (posting time) unmatched to any parameter.

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

Parameters2/5

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

Schema description coverage is only 25%, so the description needs to compensate, but it mainly restates field names. It mentions "posting time" even though there is no matching schema parameter, and it does not clarify how "song note" maps to the "song" parameter or what caption constraints exist.

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 uses a specific verb, "Write", and names the resource "post kit", then enumerates its components: caption, hashtags, song note, and posting time. It is clearer than a tautology, but "post kit" is domain jargon and the description does not explicitly distinguish this from sibling write operations such as write_file.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. "Next to the takes" provides loose context but does not tell an agent when this operation is appropriate.

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