postmoderno

Create post series

create_series

Idempotent

Start a recurring, numbered line of posts — a weekly build log, a numbered tip series. Postmoderno keeps the running number so installments never repeat or collide.

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": {
      "key": "<key>"
    },
    "name": "create_series"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	Short slug naming the series, e.g. build-log. Lowercase letters, digits, dash, underscore.
`label`	No	Human-readable name, e.g. Build log.
`template`	No	The shape each installment follows, with {n} where the number goes, e.g. Build log #{n} — what shipped this week.
`start_index`	No	Number the next installment should take, for a series that started before Postmoderno. Defaults to 1; pass 0 for a zero-based series.
`cadence_hint`	No	When it usually goes out, in plain words, e.g. every Monday 09:00. Nothing is scheduled from this — it is a note for whoever drafts the next one.

Output Schema

Name	Required	Description	Default
`key`	Yes
`status`	Yes
`next_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent, closed-world write. The description adds genuinely new context with 'Postmoderno keeps the running number so installments never repeat or collide', explaining the numbering guarantee. It does not say what happens when the key already exists or what creating a series does to existing posts, so the addition is useful but thin.

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?

A single sentence, front-loaded with the action ('Start a recurring, numbered line of posts') and followed by the differentiating benefit. No filler, no repetition of the title.

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?

With complete schema documentation, an output schema, and annotations covering the safety profile, the description only needs to sell the concept and it does. The remaining gap is relational: it never positions the tool against update_series, next_in_series, or create_post in a crowded sibling set.

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% and each of the five parameters carries a clear explanation, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond the schema (for instance, it never clarifies the interaction between key and template or the consequences of start_index).

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?

States a concrete verb and resource: 'Start a recurring, numbered line of posts', with examples (weekly build log, numbered tip series) that make the concept unambiguous. It is clearly distinguishable from create_post, but it never names its nearest siblings (update_series, next_in_series, list_series), so an agent must infer the boundary from the name alone.

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 examples imply when to reach for this tool (a repeating installment format) and the running-number note hints at the key benefit, but there is no explicit 'use X instead when…' guidance and no mention of prerequisites or how this relates to create_post.

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

All postmoderno tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?