Skip to main content
Glama

get_context

Retrieve structured context for code targets: files, modules, or symbols. Returns relationships, signatures, summaries, and decision records to understand codebase without reading full source.

Instructions

Triage card for files / modules / symbols — relationships, not source bytes.

Returns title, summary, signatures, hotspot bit, decision_record titles,
and symbol_ids to pipe into get_symbol (cheaper than Read for bodies).
Batch targets in one call. File targets above ~80 lines default to a
skeleton (every signature + top-PageRank bodies, with a verified flag —
a fraction of Read cost); ``mostly_full`` marks files where a direct
Read costs little more.

Args:
    targets: file paths, module paths, or "path::Symbol" ids.
    include: opt-in blocks: full_doc | ownership | last_change | callers
        | callees | metrics | community | decisions | skeleton.
    compact: default True; False adds structure+imports+docstrings.
    repo: usually omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNo
compactNo
includeNo
targetsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, but description covers return fields, batching, skeleton fallback, and the 'mostly_full' flag. It does not explicitly state read-only safety, but the behavior is well-explained.

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 concise and well-structured: a one-line summary, a paragraph on returns and behavior, followed by a bullet-like list for parameters. Every sentence provides value.

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?

With an output schema present, the description needn't detail return structure. It covers usage context, batching, skeleton behavior, and parameter details. Could mention error handling but is adequate for a triage tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds detailed meaning: targets accepts file/module/symbol paths, include lists opt-in blocks, compact describes output richness, repo is usually omitted. This compensates fully for the schema gap.

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 states the tool provides a 'triage card' for files/modules/symbols focusing on relationships, not source bytes. It distinguishes itself from siblings like get_symbol (for bodies) and Read (for full source).

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?

Explicitly advises batching targets, explains skeleton vs full behavior based on file size, and hints when to use get_symbol instead. The 'Args' section provides clear parameter semantics and defaults.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/repowise-dev/repowise'

If you have feedback or need assistance with the MCP directory API, please join our Discord server