Skip to main content
Glama
Sign In
Grove

Grove

by sai-softwareforest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

grove_project_get

Read-only

Retrieve a single project by name or ID to inspect its last scan time, cap warnings, and item, finding, and work-item counts—helping verify whether a scan is recent or was cut short by a cap.

Instructions

Get one project by name or id, with last_scanned_at, the last scan's cap warnings, and item, finding and work-item counts. Use to check whether a scan is recent or was cut short by a cap. 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": {
      "project": "<project>"
    },
    "name": "grove_project_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject name, or its numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly and closed-world behavior, and the description reinforces this with concrete detail: local-only operation, scans are read-only, and nothing is sent to GitHub or any other service. It also enumerates the returned signals (last scan recency, cap warnings, counts), which matters because there is no output schema. It stops short of stating what happens for an unknown project name/id.

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?

Three short sentences: what it returns, when to use it, then a trust/safety note. Front-loaded and waste-free, though the local-only sentence partly restates annotation hints rather than adding a new constraint.

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 one-parameter read tool with no output schema, the description covers the essential return signals and the safety posture. A full account of the response shape or error behavior for bad project references is absent, but nothing critical is missing for correct invocation.

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?

The schema fully documents the single `project` parameter, including that it accepts a name or numeric id, and the description matches this without adding format or resolution rules. With 100% schema coverage this is the expected baseline rather than added value.

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 ("Get one project") plus the exact lookup key (name or id) and the payload it returns (last_scanned_at, cap warnings, item/finding/work-item counts). This clearly separates it from grove_project_list and from the other single-entity getters like grove_blueprint_get.

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 an explicit use case: "Use to check whether a scan is recent or was cut short by a cap." That tells the agent when to reach for it, but it offers no exclusions or named alternatives (e.g. when to prefer grove_project_list or grove_status instead).

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