Skip to main content
Glama
Sign In
recall-kit

recall-kit

by sibrahimpa1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

project_list

Lists all projects with status and open item counts so you can review current project health and outstanding work in one view.

Instructions

All projects with status and open item counts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden; it does disclose that results are unfiltered and include status and open item counts. It says nothing about read-only safety, ordering, pagination, size limits, or permissions, leaving real gaps for a no-annotation tool.

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?

A single eight-word fragment with no filler, and the scope word "All" is front-loaded. It is a sentence fragment rather than a complete statement, which costs it a point but not clarity.

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 shape needn't be explained, and with zero parameters and no filtering the surface area is small. The description states scope and payload content, which is everything an agent needs to call it 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?

The tool takes zero parameters, and the description correctly implies there is nothing to configure by promising all projects unconditionally. Baseline 4 for a parameterless tool.

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 names a specific resource (projects) and its scope ("All") plus the fields surfaced (status, open item counts), so an agent can tell this is a bulk read of projects rather than one of the mutating siblings like project_add or project_close. It lacks an explicit verb ("list"/"retrieve"), which is the only reason it isn't a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"All projects" faintly implies unfiltered retrieval, but there is no statement of when to pick this over siblings such as project_update or memory_recall, and no prerequisites or exclusions. Any routing decision is left entirely to the agent's inference from the name.

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