Skip to main content
Glama
Sign In
keystone-mcp

keystone-mcp

by tacoda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

keystone_new_corpus

Scaffold a markdown file to capture domain notes, architecture decisions, and reasoning context for coding agents.

Instructions

Scaffold a new corpus markdown under .keystone/harness/corpus/<name>.md.

Corpus entries are reasoning / background context — domain notes, architecture decisions, idioms. Not constraints (those go in guides/) and not procedures (those go in actions/, playbooks/, skills/).

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>"
    },
    "name": "keystone_new_corpus"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
forceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits, and it does reveal the file creation path and content scope. However, it doesn't mention what `force` does, whether existing files are overwritten, whether directories are created, or what other side effects occur during scaffolding.

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 compact and front-loaded: the first sentence states the action and target path, and the second clarifies what belongs in a corpus. Each sentence earns its place with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, placement, and content categorization, and the output schema can convey return values. But it omits `force` semantics, prerequisites (e.g., an existing harness), and failure behavior, leaving notable gaps for a creation tool with no annotation support.

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 only gives meaning to `name` via the path `<name>.md`; the `force` parameter is not mentioned at all. This is insufficient for a two-parameter tool.

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 opens with a specific verb and resource: 'Scaffold a new corpus markdown under `.keystone/harness/corpus/<name>.md`.' It clearly distinguishes this from sibling tools by defining corpus entries as reasoning/background context and contrasting them with guides, actions, playbooks, and skills.

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?

The description explicitly states when to use the tool: for domain notes, architecture decisions, and idioms. It also tells when not to use it by directing constraints to `guides/` and procedures to `actions/`, `playbooks/`, and `skills/`, naming the alternatives.

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