Skip to main content
Glama
Sign In
callgraph

callgraph

by GeRiY
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

framework_view

Extract framework-specific views such as routes, middleware, validation, jobs, events, providers, DI, and views from a directory or file to map how an application is structured.

Instructions

Framework view of a directory: routes, middleware, validation, jobs, events, providers, magic, di, views. Example: {"view": "routes", "path": "routes"}. Run it on the directory that holds the definitions (a file works too).

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

Input Schema

NameRequiredDescriptionDefault
fullNoDisable the 400-line output cap.
pathYesDirectory (or file) relative to the project root, e.g. `routes`, `app`.
viewYesWhich view.
projectNoRegistered project alias; default: the server's working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.3

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the enumeration of view types and the directory-vs-file acceptance, but says nothing about output shape, truncation (the 400-line cap appears only in the schema), or read-only semantics beyond the word "view".

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?

Three tight sentences with the purpose front-loaded and the example placed right after the enumeration it illustrates. The view list is duplicated from the enum, but that duplication is functional since it tells the agent what to expect without opening 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?

For a 4-parameter, no-annotation, no-output-schema tool, the description covers purpose, valid views, example invocation, and target selection adequately. Remaining gaps — output format per view and truncation behavior — are partly covered by schema descriptions, though the description itself could say more about what comes back.

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 baseline is 3, but the description adds a concrete example call ({"view": "routes", "path": "routes"}) that shows how a view value maps to a path, which is genuinely additive. It does not touch the `full` or `project` parameters, but the schema documents those fully.

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?

The description gives a specific verb+resource ("Framework view of a directory") and immediately enumerates the concrete view kinds (routes, middleware, validation, jobs, events, providers, magic, di, views), so an agent knows exactly what class of structural information it returns. It does not explicitly contrast itself with siblings like outline or locate, which keeps it from a 5.

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

Usage Guidelines3/5

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

It offers targeting guidance — "Run it on the directory that holds the definitions (a file works too)" — which tells the agent where to point the call. However, it never states when to prefer this over outline/locate/search, nor any exclusions or prerequisites, so usage is only implied.

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