Skip to main content
Glama

Get the graph of a ground

get_graph

Get a project's information-structure graph: nodes, edges, APIs, seasons, and bugs. Slice it by root, layer, role, or season to drill into dependencies.

Instructions

Returns the tree(nodes), edges, apis, seasons, and bugs for one ground. The tree is the project's information-structure (IA) diagram — each node is a structural element (an object, or an action it performs), not a work-log entry. Node types follow the plant metaphor: trunk → limb → twig → leaf → vein. See resource umtri://rules/vocabulary. By default returns a summary view — nodes carry id/label/type/parent/season, plus a 200-char description excerpt, metadata.implements, placeholder/dormant flags (soft-deleted nodes are omitted). Pass view="full" only when you need timestamps, full descriptions, all metadata keys, or tags — that response is ~3× larger. For a large tree, read it in slices instead of all at once: rootId (+depth) for one trunk or limb; maxType for a layer (e.g. maxType="twig" = the skeleton without leaves/veins — a cheap overview); role for a cross-section; season for what was born in one season. Filters combine. Node ids come from the graph itself, so the standard drill-down is two calls: first get_graph with maxType="trunk" (or "limb") for a cheap skeleton, find the id you want, then call again with rootId set to it to get just that trunk/limb and its subtree. Control the heaviest field with descriptions: "none" drops descriptions for a pure structural overview, "excerpt" (default) gives a 200-char preview, "full" returns them verbatim when you drill into a limb. The summary response also carries shape (nodeCount, maxDepth, nodes-per-level, over-wide branches) so you can judge whether the tree is too deep or too wide without rebuilding it, a childCount on each branch node, and iaHints flagging structural smells. A bushy tree (mass at mid-levels) is healthy — don't over-nest sparse parents into twigs. Bugs default to active (open + in_progress) — pass bugStatus="all" to also see healed (resolved/closed) ones. Nodes may carry plan:true — these are the human's node-based brief (intent drawn as structure, not a prompt); read them as instructions and realize them (see umtri://rules/plan). When you slice (rootId/maxType/role/season), a connection with only ONE endpoint inside the slice is still returned, marked boundary:true, and its outside endpoint appears as a lightweight stub in externalNodes (id/label/type/role, external:true) — so cross-branch dependencies and calls never silently vanish from a slice. To follow one, call get_graph again with rootId set to that external id. The response also carries project.transplanting — when true the ground is still being transplanted (see umtri://rules/transplant): you may freely add/edit nodes in any season incl. past, and hard-delete import mistakes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoCross-section by role (structure=trunk/limb/twig, object=leaf, action=vein). Parents may fall outside the result.
slugYesGround slug (from list_projects).
viewNosummary (default) for compact nodes; full for raw shape with all fields.
depthNoWith rootId: how many levels below the root to include (0 = just the root, 1 = root + direct children). Omit for the whole subtree.
rootIdNoScope to this node and its descendants — read one trunk or limb at a time. Get the id from a prior get_graph (e.g. maxType="trunk" for a cheap skeleton). Bugs are scoped to the subtree; edges/apis that cross the subtree boundary are still returned (boundary:true) with their outside endpoint in externalNodes.
seasonNoBorn-in delta — return only nodes that first appeared in this season (season id from list_seasons): what grew that season.
maxTypeNoLayer ceiling — return only nodes at this level or higher (trunk is highest). maxType="twig" yields the structural skeleton without leaves/veins. Great for a cheap overview before drilling in with rootId.
bugStatusNoWhich bugs to include. Default "active" = wild + chasing (open + in_progress) — catched ones are healed erosion, noise on the tree. "wild" for the untouched only, "catched" for healed, "all" for every bug. Raw DB statuses still work. Use list_bugs for richer bug queries (limit/order), get_bug for one you can name.
descriptionsNoHow much of each node/bug description to include in summary view: none (drop them — lightest structural read), excerpt (200-char preview, default), or full (verbatim). Ignored when view="full" (always verbatim).
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses defaults (summary view, active bugs), size implications (full view is ~3x larger), behavior for slices (boundary nodes, externalNodes stubs, soft-deleted nodes omitted), and special cases like plan:true nodes and project.transplanting. This is far beyond what a minimal description would provide.

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?

While long, the description is organized into logical sections (summary vs full, slicing, descriptions control, shape data, bugs, plan, boundaries, transplanting). It is front-loaded with the primary purpose and every sentence contributes actionable information, with no redundancy or filler.

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?

Given that there is no output schema, the description does an excellent job of describing the response shape (summary/full fields, shape stats, childCount, iaHints), edge cases (boundary/externalNodes, transplanting), and usage workflows. For a tool with 9 parameters, this description covers all necessary context an agent needs to use it effectively.

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?

Although the schema already documents every parameter, the description adds substantial strategic context. For example, it explains that maxType='twig' is "a cheap overview" and shows how rootId, depth, and role combine to read only the relevant subtree. This enriches the schema's static definitions with real usage patterns.

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 opens by clearly stating the tool returns "the tree(nodes), edges, apis, seasons, and bugs for one ground," providing a specific verb and resource. It also distinguishes from siblings by emphasizing that it returns the whole graph, while pointing to list_bugs for richer queries and get_bug for a single named bug.

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?

The description provides explicit usage guidance, including a recommended two-call drill-down workflow: "first get_graph with maxType='trunk' (or 'limb') for a cheap skeleton, find the id you want, then call again with rootId set to it." It also explains when to use view='full', how to control payload via descriptions, and mentions that list_bugs/get_bug are better for bug-specific queries.

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/bepuljang/umtri-mcp'

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