Skip to main content
Glama

List local output projects

list_output_projects
Read-only

List local research projects by status or topic without creating or exporting a draft, so you can review available work before choosing what to open.

Instructions

Read local research projects without creating or exporting a draft.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
topic_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's 'without creating or exporting a draft' merely restates the safety profile. It adds nothing about what a 'project' contains, whether results are paginated, or how the optional filters affect the result set.

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

Conciseness3/5

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

It is a single short, front-loaded sentence with no filler, which is structurally clean. However, the brevity reads as under-specification rather than disciplined concision, since virtually every operational detail is omitted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need not be described, and the safety profile is covered by annotations. Still, for a tool with three optional filtering parameters at 0% schema coverage, the definition leaves an agent unable to use the filters correctly or know what a project record is.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions none of the three parameters. 'limit', 'status', and 'topic_id' are left entirely unexplained, including what status values are valid or what topic_id refers to, so the description fails to compensate for the coverage gap.

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 pairs a specific verb ('Read') with a specific resource ('local research projects'), which is enough to distinguish it from mutating siblings at a glance. It never states that results are returned as a list, nor differentiates it from the many other list_* siblings, so it stops short of 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?

The only guidance is the implicit negative 'without creating or exporting a draft', which hints at a read-only use case but never says when to choose this over list_review_queue, list_visual_observations, or get_topic_context. No prerequisites or exclusions are stated.

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