OKForest

View history

get_history

Read-onlyIdempotent

Who changed a tree or one of its concepts, when, and why: its commits, newest first, read from Git (changes made in OKForest and directly in Git alike). With commit, what that commit changed instead: each file's frontmatter field by field, and its lines.

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_history"
  }
}

Input Schema

Name	Required	Description
`page`	No	Which page of commits, 20 to a page; the first by default.
`tree`	No	The tree's slug, as list_trees gives it (not its name). Required unless the Forest has one tree, or `concept` names it.
`commit`	No	A commit's full SHA, as this tool lists them: what that commit changed.
`concept`	No	A concept ID, its tree first (`company:customers/acme-corp`): that concept's history, rather than the whole tree's.

Output Schema

Name	Required	Description
`more`	No	Whether there are older commits: ask for the next `page`.
`path`	No	The concept's file, when `concept` was given.
`tree`	Yes	The tree, and the commit it was read at: history ends there.
`commit`	No	What the commit changed in the tree, when `commit` was given.
`commits`	No	The commits, newest first; absent when `commit` was given.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds real context: history is read from Git and includes changes made both in OKForest and directly in Git, ordering is newest first, and the commit mode returns frontmatter fields field-by-field plus line changes.

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 tight sentences, with the primary purpose front-loaded and the alternate mode second. The second sentence is slightly elliptical ('what that commit changed instead'), but nothing is wasted.

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?

An output schema exists, so return values need not be spelled out. The description covers both operating modes, the data source, ordering, and the optionality of `tree`/`concept` context — enough for an agent to call this correctly.

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 the baseline is 3. The description earns above baseline by clarifying that `commit` is a mode switch that changes the entire operation's output shape, not merely a filter — semantics the schema alone does not convey.

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: reads the commit history of a tree or one of its concepts, newest first, sourced from Git. It also names the second mode (with `commit`, the per-file, field-by-field diff). It does not explicitly distinguish itself from siblings like get_change or list_changes, so an agent still has to infer the boundary.

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?

Gives a clear condition that switches behavior: pass `commit` to get what that commit changed instead of the commit list. That covers the primary use context well. It offers no exclusions or explicit routing against get_change/list_changes, which is the remaining gap.

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

All OKForest tools Inspect

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

Need Help?