Skip to main content
Glama
Sign In
TypeWriter MCP

TypeWriter MCP

by yurchik228336
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

replace_entry

Replace a storyline entry with a new object while retaining its ID to update content in Typewriter MCP.

Instructions

Replace a whole entry with a new object (must keep the same id).

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": {
      "page": "<page>",
      "entry": "<entry>"
    },
    "name": "replace_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
entryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions the id constraint but fails to state whether the entry must exist, what happens to tied relationships, or any side effects. Minimal behavioral context for a mutation tool.

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, front-loaded sentence that conveys the essential action and constraint with zero wasted words. Ideal conciseness.

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?

Given no annotations, no output schema, and a nested object parameter, the description is too brief. It omits likely-needed context like return values, error behavior if the id doesn't exist, and whether the page must exist. Significant gaps remain.

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 0%, so the description must compensate. It adds context about the entry (must keep same id) but does not explain the 'page' parameter or the structure/required fields of the entry object. Only partial compensation.

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 clearly states the action ('Replace'), the resource ('a whole entry'), and the key requirement ('must keep the same id'). This distinguishes it from sibling tools like update_entry (partial updates) and add_entry (new entries).

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 phrase 'replace a whole entry' implies this is for full replacement rather than partial field updates, but it does not explicitly mention alternatives or when to prefer this over update_entry. Usage context is implied, not explicit.

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

Deploy Server

Other Tools