Skip to main content
Glama

Onplana

by io.github.Onplana
OverviewDiscussionsAdmin

list_my_tasks

Read-onlyIdempotent

Answers "what is on my plate", "my tasks this week" and "what do I have overdue" from the user's Onplana workspace. List tasks assigned to YOU (the calling user), and tasks you collaborate on. Resolves "me" server-side - no need to pass an assignee id. Each row's role is "assignee" or "collaborator"; a collaborator row also names the assignee in assigneeName. Optional scope: "assigned" (the default, the tasks above) or "managed", every task in the projects you manage (projects you own, or where your project role can edit the project), whoever holds it; a row there you are not on has role "manager" and names its assignee. Optional filters: status (TODO / IN_PROGRESS / REVIEW / DONE / BLOCKED), overdueOnly (only tasks past due date and not DONE). Default returns 25, max 50. PREFER list_assigned_tasks when YOU are an AI agent - that variant adds agentBrief, projectName, and hasOpenPrompt to each row so you can start work without a follow-up get_task. Use list_tasks instead when querying across multiple users.

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25, max 50.
scopeNo"assigned" (default): tasks you hold or collaborate on. "managed": every task in the projects you manage.
statusNo
overdueOnlyNoOnly return tasks past their due date and not yet DONE.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "\"assigned\" (default): tasks you hold or collaborate on. \"managed\": every task in the projects you manage.",
+  "enum": [
+    "assigned",
+    "managed"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, lowering the bar. The description still adds real value: server-side resolution of "me", the meaning of the returned `role` and `assigneeName` fields, what the "managed" scope includes, and the default 25 / max 50 limit behavior. It does not discuss pagination beyond the limit or ordering.

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?

Purpose and natural-language triggers are front-loaded, followed by scope, filters, limits, and routing. It is long, but nearly every clause carries distinct information; the closing routing paragraph is dense yet justified given the large sibling set.

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?

For a read-only list tool with no output schema, the description covers interpretation of returned rows (role, assigneeName, manager role), scope semantics, filters, and defaults. Nothing material an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 75%, so the schema documents most parameters. The description still adds substantive meaning: it defines "managed" precisely (projects you own or can edit, whoever holds the task), lists the status enum values, and explains overdueOnly as past-due and not DONE. Limit is only restated (default 25, max 50) with no added semantics.

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?

Names a specific verb and resource (list tasks) and scopes it precisely to the calling user via server-side "me" resolution. It distinguishes itself from siblings by explicitly routing to list_assigned_tasks and list_tasks with conditions, so an agent can pick it without opening any schema.

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?

Provides explicit when-to-use guidance including natural-language triggers ("what is on my plate", "my tasks this week", "what do I have overdue") and two named alternatives with the condition that selects each. The scope=assigned vs managed distinction further clarifies when the tool widens its reach.

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

All Onplana toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources