Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

project_notes_write

Save project-specific coding instructions and conventions as notes without altering source files.

Instructions

Save project-specific coding instructions and conventions. Does not alter source files.

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": {
      "text": "<text>"
    },
    "name": "project_notes_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesProject notes, up to 12,000 chars

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description adds useful scope reassurance that source files are untouched. However, for a write/persist tool it never says whether existing notes are overwritten or appended, or where the notes are stored — meaningful gaps beyond annotations.

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?

Two short sentences, zero filler, with the core action stated first and the clarifying scope constraint second.

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 one-parameter tool with full schema coverage and annotations covering safety, the definition is nearly sufficient. The remaining gap is persistence semantics — overwrite vs. append and durability — which would matter to an agent deciding whether to write incrementally.

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 coverage is 100% with a single required parameter whose description already states the 12,000-char limit. The description conveys what kind of content belongs in 'text' but adds no format, structure, or validation detail beyond the schema, so baseline 3 applies.

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?

Specific verb+resource: 'Save project-specific coding instructions and conventions' clearly states it persists notes content. The clause 'Does not alter source files' begins to differentiate it from write_file, though it doesn't name that sibling explicitly.

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 exclusion 'Does not alter source files' implies the usage boundary versus general file-writing tools, and the sibling project_notes_read implies a read/write pairing. But there is no explicit when-to-use or when-not-to-use statement naming the alternative.

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