Skip to main content
Glama
permanu

SuperSkill

by permanu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

project_context

Read-only

Retrieves a project's context document for AI agents, auto-detecting the project from the current working directory or using a specified slug, with optional summary or full detail.

Instructions

Get the context document for a project. Auto-detects project from CWD if not specified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoProject slug. If omitted, auto-detected from CWD.
max_tokensNoEstimated content token budget, also passed through in full detail
detail_levelNoDetail level (default summary)
workspace_pathNoAbsolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.1
    • addedInput schema / properties / workspace_path
      Added value: +{
+  "description": "Absolute thread workspace directory; must map to this project. Omit only when the server cwd is the thread workspace.",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.13.0
    • addedInput schema / properties / max_tokens
      Added value: +{
+  "description": "Estimated content token budget, also passed through in full detail",
+  "maximum": 50000,
+  "minimum": 256,
+  "type": "integer"
+}
  3. First observedv0.6.1

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe read operation, lowering the bar. The description adds the auto-detection trait, but says nothing about how detail_level or max_tokens affect the result or what the returned document contains.

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?

Two short sentences, front-loaded with the core purpose and followed by the auto-detect caveat. Both sentences earn their place, though the overall brevity leaves real gaps unaddressed.

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 read-only tool with a fully documented schema and no output schema, the description is minimally adequate. It omits what the 'context document' contains and how it relates to the 'generate_context' sibling, which an agent would need to choose correctly.

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 description coverage is 100%, so the schema already documents all four parameters, establishing a baseline of 3. The description only echoes the auto-detect behavior for 'project' and adds no syntax or format detail beyond the schema.

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 ('Get the context document for a project'), which is clear. However, it does not distinguish itself from the sibling 'generate_context', leaving ambiguity about whether this retrieves an existing document versus producing one.

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?

The only guidance is the CWD auto-detection behavior, which is really a parameter default rather than usage context. It never says when to reach for this tool instead of 'generate_context' or other context-related siblings.

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