Skip to main content
Glama

The areas of the codebase

graph_areas
Read-only

Map a repository into functional areas, then inspect any area's key members and linked areas to get oriented in unfamiliar code. Read-only, local, and returns JSON.

Instructions

The codebase split into areas: groups of functions and classes that work together, grouped folder by folder and named after the folder and the member the rest of the code depends on most, with its size, folders and links to other areas. Pass an area id to get its members, most important first, and the areas it links to. Use it to get oriented in an unfamiliar repository. Returns JSON. Read-only and local.

Works without SKYLOS_API_KEY and has no daily limit: it reads the repository on this machine and sends nothing to Skylos Cloud.

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": "graph_areas"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoArea id from a previous call, to list its members and linked areas
pathNoProject directory. A relative path resolves against the MCP server's working directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.6.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, and the description goes further by disclosing auth requirements (works without SKYLOS_API_KEY), absence of a daily limit, and data locality (reads the repo on this machine, sends nothing to Skylos Cloud). It also flags that the result is ordered "most important first", which the agent cannot learn from annotations.

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?

Front-loads the definition of an area before the usage hint, then a short operational note. The second paragraph on API keys and limits is valuable but slightly padded by restating "read-only and local" plus "sends nothing to Skylos Cloud".

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?

An output schema exists, so return values need not be spelled out, and the description covers what the agent still needs: the shape of the data model, both call modes, safety profile and auth/limit constraints. Nothing required to invoke it correctly is absent.

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 100%, so both parameters are already documented and the baseline would be 3. The description adds behavior beyond the schema: omitting the area id yields the area overview, while supplying an id switches to members-plus-linked-areas and returns them ordered by importance.

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 the specific resource (codebase split into areas of co-working functions/classes, named after folders and their most depended-on member) and the two operating modes (no argument = area overview, area id = members and linked areas). It never names a sibling to contrast with, so the agent must infer the boundary against graph_find/graph_describe/graph_show on its own.

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?

"Use it to get oriented in an unfamiliar repository" gives a clear positive trigger for the tool. There are no exclusions or named alternatives for when a different graph tool is the better choice, which is the only thing missing.

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