Skip to main content
Glama
Sign In

OKForest

by ai.okforest
OverviewDiscussionsAdmin

Report on a tree's links

get_graph_report
Read-onlyIdempotent

How a tree's concepts link to each other: the most linked concepts, those with no links at all, and its areas (concepts more linked to each other than to the rest), with how many links join each pair of areas. An area joined to no other shows where the tree lacks links between its parts.

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

Input Schema

NameRequiredDescriptionDefault
treeNoThe tree's slug, as list_trees gives it (not its name). Required unless the Forest has one tree.

Output Schema

NameRequiredDescriptionDefault
treeYesThe tree, and the commit it was read at.
areasYesThe tree's areas: concepts more linked to each other than to the rest.
linksYesHow many links join one concept to another.
orphansYesConcepts with no links to or from another concept.
conceptsYesHow many concepts the tree has.
mostLinkedYesThe concepts most linked to, most first (up to 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world) and an output schema exists, so the bar is lower. The description still adds genuine domain context beyond structured data by defining what an 'area' is and explaining that an area joined to no other signals missing links between parts, which shapes how an agent interprets results.

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?

Two sentences that lead with the resource and then the report contents; little waste. The closing clause about an area joined to no other is interpretive rather than purely definitional, but it earns its place by telling the agent how to read a notable result.

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 read-only analytical tool with a documented single parameter and a full output schema, the description covers what the report contains and how to interpret its most unusual signal. The remaining gap is routing guidance against get_links and find_path, which is a usage-dimension issue rather than missing essentials.

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

Parameters3/5

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

Only one parameter and schema description coverage is 100%, with the schema already explaining that it takes a slug (not a name) and is optional when the Forest has a single tree. The description adds nothing about the parameter, so the baseline 3 applies.

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 names the resource (a tree's link structure) and enumerates the exact report contents: most-linked concepts, isolated concepts, and areas with inter-area link counts. It is clear what the tool produces, but the verb is implicit ('how a tree's concepts link') and it never names the sibling it differs from, so an agent must infer that get_links returns raw edges while this returns an aggregate.

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?

Usage is only implied: the aggregate nature of the report suggests reaching for it when structural overview is wanted rather than individual links. No when-to-use statement, no exclusions, and no mention of get_links or find_path as alternatives, which is a real gap given how closely those siblings overlap.

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

All OKForest toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources