Skip to main content
Glama
Sign In
code-index

code-index

by RaviIITk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_context

Summarize the structure of a file or folder in your workspace, showing names, signatures, and line ranges. Adjust depth to drill down from folders to functions or classes.

Instructions

Token-cheap structural summary rooted at a file or folder path (workspace-relative). Structural facts only (names, signatures, line ranges) — no docstrings, use get_details for those. Increase depth to drill from folder -> file -> function/class detail.

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": {
      "path": "<path>"
    },
    "name": "get_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
depthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions 'token-cheap' (cost awareness) and the structural nature, but does not explicitly state read-only or side-effect-free behavior. Adequate but not fully transparent.

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?

Two sentences, front-loaded with the core purpose, then specific details and related tool. No extraneous words. Every sentence earns its place.

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

Completeness5/5

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

For a simple tool with 2 params and no output schema, the description covers what it returns, how to use the parameters, and how it relates to a sibling tool. It is complete for the context.

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

Parameters4/5

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

Schema coverage is 0%, so description must add meaning. It explains 'path' as workspace-relative and 'depth' as drilling from folder to detail levels. This adds significant value beyond the schema's names and default.

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 returns a 'structural summary' with 'names, signatures, line ranges' for a file or folder path. It distinguishes from get_details by excluding docstrings. This is specific and differentiates from siblings.

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

Usage Guidelines4/5

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

The description explicitly advises using get_details for docstrings, implying that get_context is for structural info only. It does not explicitly state when not to use it, but the guidance is clear and helpful.

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