Skip to main content
Glama

tree_get

Read a Quern tree at a path, optionally pruned to depth, to inspect its node kinds, rules, solvers, and derived branches before editing or linking. Set kinds to list kinds beneath the node.

Instructions

Read the Quern at path (default: whole tree), pruned to depth levels if given. Each slice arrives with its own semantics: the kinds present (with the operations they afford — full contract at operation://{kind}/{name}), the rules that apply, the solvers whose reads cover the slice. A workspace may expose derived branches (recomputed from their source on every read) — inspect and link to them, don't edit. kinds adds kinds_under: the kinds beneath the node at any depth, with how many of each (a walk of the branch, so asked for, not sent on every read).

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

Input Schema

NameRequiredDescriptionDefault
pathNo
depthNo
kindsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.13
    • addedInput schema / properties / kinds
      Added value: +{
      +  "default": false,
      +  "title": "Kinds",
      +  "type": "boolean"
      +}
  2. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden and it does disclose meaningful traits: slices carry semantics, derived branches are recomputed from source on every read, and `kinds` triggers an extra walk that is 'asked for, not sent on every read' (a useful cost hint). It does not state error behavior for missing paths, permission requirements, or payload size limits, so read-only safety is only implied by the verb 'Read'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main action is front-loaded, but the prose is dense and parenthetical-heavy, with nested em-dash clauses that slow parsing. Several phrases (e.g. 'asked for, not sent on every read') are valuable while others restate the same read-semantics idea twice.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 structure needn't be explained, yet the description still spends effort on slice contents while omitting error cases and sibling routing. For a three-parameter tree reader with no annotations, it is adequate but not fully complete.

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 0%, so the description must compensate and largely does: `path` is described with its default (whole tree), `depth` as pruning to N levels, and `kinds` as adding `kinds_under` with counts plus the cost of the extra walk. Data types and the interaction of depth with kinds_under depth are left unstated.

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 a specific verb and resource ('Read the Quern at `path`') with scope ('default: whole tree') and pruning behavior, and the mention of kinds/rules/solvers distinguishes it from write-oriented siblings like tree_set and tree_delete. The term 'Quern' is unexplained domain jargon, which keeps it from a 5 for an agent without prior context.

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 gives one real usage rule — derived branches should be inspected and linked, not edited — but offers no guidance on when to call tree_get versus tree_brief, tree_find, or tree_check, despite 14 siblings. Usage is implied by the read semantics rather than stated as decision criteria.

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