Skip to main content
Glama

set_project

Rewrite PROJECT.md sections—intent, blocks, and open items—as one atomic change while preserving unspecified sections and Decisions.

Instructions

Rewrite sections of PROJECT.md as ONE change: intent (at most 2000 characters), blocks (an array of at most 50 { name, does, status }) and open (an array of at most 50 non-empty strings). Sections not given and Decisions stay.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNoe.g. ["route the board"]
blocksNoe.g. [{ name: "CAN", does: "TJA1051 transceiver", status: "placed" }]
intentNoOne paragraph

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses atomicity ('as ONE change'), the preservation semantics for omitted sections and Decisions, and hard limits (2000 characters, 50 blocks, 50 open items, non-empty strings). It does not describe what happens if constraints are violated or what the response contains, which keeps it short of a 5.

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?

A single dense sentence with no filler; the atomicity and preservation guarantees are front-loaded before the field-by-field constraints. It is slightly run-on and would read better split, but nothing is redundant.

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?

For a three-parameter write tool with no annotations and no output schema, the description covers the essentials: what gets replaced, what is preserved, and the size limits on each field. The main remaining gap is the outcome of an invalid or oversized payload, which an agent would want to know before calling.

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%, so baseline is 3, but the description adds constraints absent from the schema itself: the 2000-character cap on intent, the 50-item cap on both arrays, the non-empty-string requirement for open, and the required name/does/status triple per block. That is genuine added meaning beyond the structured fields.

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 specific verb and resource: 'Rewrite sections of PROJECT.md'. The listed fields (intent, blocks, open) make the scope concrete, and the write semantics clearly distinguish it from the read-only sibling project_status without needing to name it.

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?

Usage is implied rather than stated: the phrase 'as ONE change' and the preservation rule ('Sections not given and Decisions stay') tell the agent this is a partial/merge update, which is actionable context. However, there is no explicit when-to-use versus when-not guidance, and no mention of prerequisites such as an existing PROJECT.md or validation failure handling.

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