Skip to main content
Glama

Get Context

get_context

Retrieve full project context as formatted text, optionally filtered by a dot-notation path to focus on specific fields such as project name or tech stack.

Instructions

Get the full project context as formatted text. Optionally filter by dot path (e.g. 'tech_stack.languages').

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
dot_pathNoOptional dot-notation path to get a specific field (e.g. 'project.name', 'tech_stack.languages'). Leave empty to get the entire context.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does signal the return is 'formatted text' and that omitting dot_path yields the entire context, which is useful. It says nothing about behavior when a dot path is invalid or absent, nor about output size for a full-context read.

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 purpose followed by the optional filtering behavior. Efficient overall, with only minor redundancy in re-stating the dot-path example already present in the schema.

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?

An output schema exists, so return shape need not be explained, and both optional parameters are fully documented in the schema. For a simple two-parameter read tool the description is nearly sufficient, missing only error/edge behavior for invalid dot paths.

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 both parameters are already documented in the schema, and the description's dot-path example duplicates the schema's own example. Baseline 3 applies since the description adds no meaning 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 full project context as formatted text.' An agent can distinguish it from mutation siblings like update_context or reset_context. It does not, however, distinguish itself from read-only siblings such as project_info, get_prd, or export_context_markdown.

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?

No when-to-use or when-not-to-use guidance and no named alternative. The only guidance is parameter-level ('optionally filter by dot path'), which does not tell an agent whether to reach for this versus project_info or get_prd when it wants project information.

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