Medium Blog MCP Server

by Navneet1710

Overview Schema Source Related Servers Discussions Admin

Python

Local

Save Outline

save_outline

Save the generated outline to the database for a given session ID.

Instructions

Save the generated outline to database

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": {
      "session_id": "<session_id>",
      "outline_data": "<outline_data>"
    },
    "name": "save_outline"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes	Active session ID
`outline_data`	Yes	Generated outline JSON with title, subtitle, sections, etc.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description only says the outline is saved to a database. It does not disclose whether saving overwrites an existing outline, whether it requires prior approval, or what side effects occur beyond persistence. No annotations are present to supplement this.

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 a single, focused sentence with no superfluous words. It is appropriately concise for the simple operation it describes.

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?

For a basic save operation, the description is understandable and actionable. However, it omits any mention of return values, error conditions, or dependencies on other steps in the workflow, which limits completeness in a larger agent context.

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 schema provides full coverage for both parameters with descriptions, so the baseline is 3. The tool description adds no extra meaning beyond the schema, leaving parameter semantics entirely to the schema.

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 the action ('Save') and the resource ('generated outline') with a destination ('to database'). It is distinguishable from sibling tools like generate_outline or approve_outline, though it does not explicitly name them.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of preconditions (e.g., outline must be generated or approved) or contextual cues that should trigger saving.

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