Skip to main content
Glama
Sign In
Grove

Grove

by sai-softwareforest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

grove_knowledge_get

Read-only

Fetch a knowledge document by key and optional revision to read its full content after search results; specify project when the same key exists in multiple projects.

Instructions

Fetch a knowledge document by key: the latest revision, or a given revision number. Keys are unique per project (and at workspace level); pass project when the same key exists in more than one project. Without project, a workspace-level document wins. Use after grove_knowledge_search to read a full document. Grove is local only: scans are read-only and nothing is sent to GitHub or any other service.

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": {
      "key": "<key>"
    },
    "name": "grove_knowledge_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
projectNoProject name or id, to pick that project's document.
revisionNoRevision number; latest if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false; the description reinforces this with 'local only' and 'nothing is sent to GitHub or any other service', and adds a non-obvious resolution rule (workspace-level document wins without project). It does not say what happens when the key is missing or what the response contains, which keeps it short of a 5.

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?

Four sentences, front-loaded with the core action and the disambiguation rules before the sibling pointer and trust note. Every sentence carries information, though the closing local-only sentence is somewhat tangential to invocation and could be tightened.

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?

No output schema exists, but for a document-fetch tool the key inputs, resolution precedence, and safety profile are all covered. The only real gap is that it never characterizes the returned document (content plus revision metadata) or the not-found behavior, which an agent might want.

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 67% and the description meaningfully extends it: key uniqueness is scoped per project and at workspace level, and project selection is framed as disambiguation rather than a filter. The revision parameter's default is only restated from the schema, so it adds no new information there.

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 ('Fetch a knowledge document by key') plus the scope variants (latest revision or a given revision number). It explicitly separates itself from grove_knowledge_search ('Use after ... to read a full document'), so an agent can pick between search and fetch without inspecting either schema.

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?

Gives an explicit when-to-use rule: call this after grove_knowledge_search when the full document is needed. It also gives concrete guidance for the ambiguous case, telling the caller to pass project when the same key exists in more than one project and noting the workspace-level precedence otherwise.

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

Deploy Server

Other Tools