List quests, optionally filtered by status and/or workspace. Shows each quest's id; at most 50 unless a limit is given.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Default 50 | |
| status | No | ||
| workspace | No | Project/workspace to scope to (defaults to this connection's workspace; isolates work streams within your account) |
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | ||
| count | Yes | ||
| total | Yes | ||
| quests | Yes | ||
| status | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / noteAdded value: +{
+ "type": "string"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "type": "integer"
+ },
+ "quests": {
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "priority": {
+ "type": "string"
+ },
+ "status": {
+ "type": "string"
+ },
+ "title": {
+ "type": "string"
+ },
+ "workspace": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "title",
+ "priority",
+ "status",
+ "workspace"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "enum": [
+ "pending",
+ "completed",
+ "all"
+ ],
+ "type": "string"
+ },
+ "total": {
+ "type": "integer"
+ }
+ },
+ "required": [
+ "status",
+ "count",
+ "total",
+ "quests"
+ ],
+ "type": "object"
+}Input schema / properties / limitAdded value: +{
+ "description": "Default 50",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral burden. It usefully discloses the default cap of 50 results and that each quest's id is shown, but it does not cover permissions, whether status 'all' has special behavior, or other operational constraints.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is two efficient sentences with the main purpose front-loaded. Every clause contributes useful information about filtering and output limiting.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with an output schema, the description covers the core operation, filters, and result cap. It is nearly complete, though it could better situate the tool relative to its very similar sibling wyrm_all_quests.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%, so the schema already documents most parameters. The description adds useful context that results are capped at 50 unless a limit is supplied, but it does not clarify status semantics beyond the enum or add much about workspace scoping beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 quests. It also mentions optional status/workspace filtering, which makes the operation clear. However, it does not distinguish this tool from the closely named sibling wyrm_all_quests.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for listing quests and notes optional filters by status and/or workspace. It does not explicitly say when to use this tool instead of wyrm_all_quests or other quest-related siblings, nor does it describe exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.