Skip to main content
Glama
Sign In
Grove

Grove

by sai-softwareforest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

grove_work_list

Read-only

List a project's work items with pagination and optional status filtering to quickly see what is open, in progress, in review, done, or blocked.

Instructions

List a project's work items, paginated, optionally only those in one status (ready, in_progress, review, done, blocked). Use to see what is open. 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_work_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (default 50, max 200).
offsetNoNumber of items to skip.
statusNo
projectYesProject name, or its numeric id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description reinforces local-only operation and no external service calls, and mentions pagination, but it adds little beyond the annotation safety profile and schema pagination fields, and does not explain ordering or page traversal.

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?

The description is short and front-loads the main list operation and status filter. The local-only sentence is relevant but slightly repetitive with the annotations.

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 low-complexity list tool with annotations and no output schema, the definition gives enough to invoke it correctly: required project, optional status, and pagination. Return ordering and response shape are not described, but those are less critical here.

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 75%, so the schema already documents limit, offset, and project. The description adds the status filter concept and lists its enum values, but does not add further meaning such as ordering, default behavior, or how offset interacts with filtered results.

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?

The description states a specific verb and resource: it lists a project's work items and supports status filtering. It is clearly a list operation rather than get/create/update, though it does not explicitly name a sibling alternative.

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 phrase 'Use to see what is open' gives clear intended usage, and the optional status filter indicates a common narrowing case. It does not state when not to use it or name a sibling such as grove_work_get for single-item retrieval.

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