Skip to main content
Glama

Add Key File

add_key_file

Register a key file and its purpose in the project context so assistants can track important files and their roles.

Instructions

Register a key file with its purpose in the project context.

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": {
      "file_path": "<file_path>",
      "purpose": "<purpose>"
    },
    "name": "add_key_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNoOptional extended notes about the file.
purposeYesWhat this file does (one sentence).
file_pathYesPath to the file (relative to project root).
root_pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full disclosure burden. It implies a persistent mutation of the project context but says nothing about duplicate handling, whether existing entries are overwritten, required permissions, or whether the context store must exist first; an output schema does relieve it of explaining return values.

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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the source of the missing guidance rather than a model of tight scoping.

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?

For a four-parameter context-mutation tool, the description covers the core action and the schema plus output schema cover inputs and returns. The remaining gaps are behavioral: no mention of context initialization prerequisites or what happens on re-registering the same path.

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%, so all four parameters including optional details and root_path are already documented in the schema. The phrase "with its purpose" loosely maps to the required purpose field but adds no syntax, format, or constraint information 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?

The description names a specific verb+resource pair ("Register a key file") and the destination store ("project context"), so an agent can tell it is not a generic file write. It stops short of differentiating itself from close siblings such as add_to_context_list or update_context, which an agent may reasonably confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite (e.g. that a context must already be initialized), and no indication of when to prefer this over add_to_context_list or add_decision. The agent must infer the selection rule entirely from the name.

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