Skip to main content
Glama

write_resource

Persist validated edits to existing tasks or epics by replacing, inserting, or appending content, then reconcile indexes and diagnostics.

Instructions

Use when you want backlog-mcp to validate and canonically persist an existing entity edit before reporting success. For ordinary repository prose edits, use your native Edit tool; reconciliation updates indexes and diagnostics afterward. Create and transition entities through the substrate-declared intent tools.

  • The append command will add content to the end of the body, automatically adding a newline if needed. Notes for using the str_replace command:

  • The old_str parameter should match EXACTLY one or more consecutive lines from the original body. Be mindful of whitespaces!

  • If the old_str parameter is not unique in the body, the replacement will not be performed. Include enough context to make it unique.

  • The new_str parameter should contain the edited lines that should replace the old_str

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asNoOPTIONAL agent identity for this write — an AGENT- doc id or declared principal (e.g. "aime:granite"). Values are trimmed; whitespace-only is treated as absent.
idYesTask or epic ID, e.g. TASK-0001 or EPIC-0002
homeNoSelect the document home for this call. Overrides bridge defaults: global uses the user-wide home; project uses project_root or the bridge project.
operationYesOperation to apply to the body
project_rootNoProject root for this call. Overrides the bridge project root and selects the project home.
Behavior4/5

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

No annotations provided, so description carries full burden. It explains validation and persistence behavior, and includes operational details for commands (append auto-newline, str_replace uniqueness). Could mention error handling or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, but the command usage notes are lengthy and could be summarized more concisely. Every sentence is useful, but structure could be tighter.

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?

Provides usage guidelines and operational details for a complex tool with nested parameters. Lacks return value or error handling info, but overall comprehensive given no output schema.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. The description adds operational notes for operation types (e.g., uniqueness of old_str, auto newline for append), which go beyond schema definitions.

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 tool's purpose: to validate and canonically persist an existing entity edit. It distinguishes this from ordinary prose edits (use native Edit tool) and creation/transition (use intent tools).

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?

Explicitly says when to use this tool and when not, providing direct alternatives: 'For ordinary repository prose edits, use your native Edit tool; Create and transition entities through the substrate-declared intent tools.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gkoreli/backlog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server