Skip to main content
Glama

SourceGeek

List a project's tasks

list_tasks
Read-only

List one SourceGeek project's tasks (removed ones left out), in board order, with the project's brief. Each task has its key (e.g. SBE-12), title, status (To do, Waiting, In progress, Working, Needs input, Needs approval, Ready for review, Failed or Done), assignee, progress through its steps while it runs, the tasks it waits on, its repeat schedule if it recurs, and its URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "list_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesThe project's id (prj_…) or key (e.g. SBE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false, so the safety profile is covered; the description adds useful behavior beyond them: excluded deleted tasks, board-order sorting, inclusion of the project brief, and in-flight step progress. It doesn't mention pagination or result-size limits, which is the main remaining gap.

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?

Front-loaded with the verb, resource, and scope in the first clause; the long field enumeration is justified because there is no output schema. Slightly dense as a single sentence, but every clause carries information.

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?

With no output schema, the detailed enumeration of returned task attributes (key, title, status values, assignee, step progress, dependencies, recurrence, URL) does real work and makes the result shape predictable. Missing only ordering/pagination caveats for large projects.

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 coverage is 100% and already explains the project id/key format with examples, including the maxLength constraint. The description adds no additional meaning about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource ('List one SourceGeek project's tasks') and scopes it to a single project, distinguishing it from workspace-level siblings like list_projects and action siblings like plan_tasks/start_tasks. The parenthetical about removed tasks further pins the semantics.

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

Usage Guidelines3/5

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

The single-project scope and 'removed ones left out' framing imply when this tool is appropriate, but it never states when to use it versus plan_tasks, start_tasks, or list_projects, nor any prerequisites. Guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources