Skip to main content
Glama
Sign In

Designers

by com.allthepossibles
OverviewDiscussionsAdmin

Save project context

save_project_context
Read-only

Pro. Save named project context (brand notes, a DESIGN.md, past decisions, personas) against the Pro key, up to 20 items of 50,000 characters, so later sessions and prompts can reuse it.

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": {
      "name": "<name>",
      "content": "<content>"
    },
    "name": "save_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYese.g. design-md, brand-voice
contentYesThe text to save

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The description provides crucial behavioral limits not in the schema, such as the capacity of 'up to 20 items' and the character limit of '50,000 characters.' However, the tool's description ('Save') appears to contradict the annotations (which include 'readOnlyHint: true').

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 tool is described in a single, focused sentence. It is highly efficient and avoids unnecessary jargon or fluff, front-loading the core functionality.

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?

Given that the output schema is not defined, the description is quite complete. It provides the necessary constraints (item count, character limit) and the utility of the function.

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?

While the schema defines the parameters, the description adds semantic depth by providing concrete naming conventions (e.g., 'design-md', 'brand-voice') and explaining the purpose of the input ('so later sessions and prompts can reuse it'), which is valuable context.

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 defines the tool's purpose: to 'Save named project context.' It provides concrete examples of what kind of context is saved (brand notes, DESIGN.md), which effectively distinguishes it from specialized lint or audit tools.

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 tool implies usage by stating that saving context allows 'later sessions and prompts can reuse it.' However, it does not provide explicit guidance on the optimal time to use this tool relative to others (e.g., whether this should be run before or after a specific generation task).

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

All Designers toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources