perseus

perseus_agora

Read-only

Retrieve tasks from project task board files. Filter by status to show open, in progress, or completed tasks.

Instructions

List tasks from the project task board (tasks/*.md files). Use to see what is open, in progress, or completed. Filter by status. Read-only; returns task array with id, title, status, scope.

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

Input Schema

Name	Required	Description	Default
`status`	No	Filter tasks by status: open, in_progress, completed, cancelled

Output Schema

Name	Required	Description	Default
`tasks`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.0.7Jun 10, 2026

changedInput schema / properties / status / description

Previous value: -"status= modifier for @agora"New value: +"Filter tasks by status: open, in_progress, completed, cancelled"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "tasks": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Task identifier",
+            "type": "string"
+          },
+          "scope": {
+            "description": "Effort estimate",
+            "type": "string"
+          },
+          "status": {
+            "description": "Task status",
+            "type": "string"
+          },
+          "title": {
+            "description": "Task title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Description explicitly marks as read-only and specifies return fields (id, title, status, scope). Annotations already indicate readOnlyHint, but description adds return structure detail.

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?

Two concise sentences with no wasted words. Front-loaded with primary action and resource.

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?

Covers source, filtering, and return format. With output schema present, description adequately compresses key information for a simple tool.

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 already covers status parameter with description listing values. Description reinforces 'Filter by status' but adds minimal new information beyond schema.

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?

Description clearly states it lists tasks from project task board (tasks/*.md files). The verb 'list' and specific resource distinguish it from generic list tools like perseus_list.

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?

Indicates usage for seeing task statuses (open, in progress, completed) and filtering by status. Does not explicitly exclude other tools, but context is clear.

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