Skip to main content
Glama
Cafelatte1

FronyBoard

by Cafelatte1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_projects

List all tracked projects with their key, name, repo, status and activity summary so you can discover which board keys exist. Archived projects are excluded unless requested.

Instructions

Use it when the user asks which projects are tracked (project list, which boards exist).

List every project (key, name, description, repo, status, meta) — how to find out
which keys exist. Archived ones are left out unless `include_archived` is set.

Each entry carries a `summary`: its open periods, task counts by status and
`last_activity` (the newest task update). No milestones or task detail: get_roadmap
for the plan, get_status for per-period progress, list_tasks for the tasks.

Input Schema

NameRequiredDescriptionDefault
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden well: it discloses returned fields, archived filtering, summary contents, and explicitly excludes milestones and task detail. It does not mention pagination, ordering, or access constraints, but for a read-only listing tool the core behavior is clearly described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the usage condition, then the listing behavior and parameter effect, then return-value details and sibling guidance. Each sentence adds distinct information, and the structure makes it easy to scan without unnecessary repetition.

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?

Given there is no output schema and only one parameter, the description is complete: it explains what is returned, what summary data accompanies each project, what is excluded, and when to use sibling tools instead. An agent can invoke and interpret this tool correctly from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, so the description must explain the only parameter. It does so directly: archived projects are omitted unless include_archived is set, which gives the parameter clear semantic meaning beyond the schema's bare boolean title.

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?

The description gives a specific verb and resource ('List every project') and explicitly states the user scenario it serves: when the user asks which projects are tracked. It also distinguishes the tool from siblings by saying it returns project identity fields and summary counts rather than roadmaps or task detail.

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?

It explicitly says when to use it ('when the user asks which projects are tracked') and names alternatives for adjacent needs: get_roadmap for the plan, get_status for per-period progress, and list_tasks for tasks. It also clarifies archived-project behavior via the include_archived parameter.

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