Skip to main content
Glama
Sign In

OKForest

by ai.okforest
OverviewDiscussionsAdmin

Find how two concepts connect

find_path
Read-onlyIdempotent

The shortest chain of links joining two concepts of one tree, following links either way (at most 6 links), each step saying which way its link points. For questions like "how does A relate to B?".

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "find_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe other concept's ID, in the same tree as `from`.
fromYesConcept ID, its tree first: `company:product/okforest-product-brief`. In a Forest of one tree, the tree may be left out.

Output Schema

NameRequiredDescriptionDefault
treeYesThe tree they're in, and the commit it was read at.
stepsYesThe concepts from `from` to `to`, both included; empty when they aren't joined.
connectedYesWhether a chain of at most 6 links joins them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds genuinely new behavioral context: the path is capped at 6 links, links are followed in either direction, and each step indicates the link's direction.

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 behavior and capped with the use case. No wasted words; every clause adds a distinct constraint (shortest chain, one tree, bidirectional, 6-link cap, direction markers).

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?

With an output schema covering return values and annotation-covered safety, the description supplies the remaining caller-relevant facts: traversal direction, depth cap, and same-tree requirement. Only minor things like behavior when no path exists are missing.

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?

Schema coverage is 100%, including the tree-prefixed concept ID format, so baseline is 3. The description adds the implicit 'both concepts in the same tree' constraint, but offers no additional syntax or format detail beyond the schema.

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?

States a specific verb and resource: it returns the shortest chain of links joining two concepts, with the max of 6 links and bidirectional traversal. This is clearly distinguishable from siblings like get_links (raw links) and search_concepts (lookup).

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 closing sentence gives a concrete triggering question pattern ('how does A relate to B?'), which tells the agent when this tool is the right choice. It doesn't explicitly name alternatives or exclusions, but the use case is clear.

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