Skip to main content
Glama

get_completed_tasks

Read-onlyIdempotent

Obtiene las tasks completadas del usuario autenticado (no disponible para tokens sb_*)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir = TODOS los workspaces de la persona, en una sola llamada

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious context: results are scoped to the authenticated user and the tool is unavailable to sb_* tokens, an auth constraint an agent could not infer elsewhere. It does not mention ordering, pagination behavior, or how completions are dated, keeping it out of 5 territory.

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?

A single compact sentence with the key scope upfront and no filler. It is efficient, though the parenthetical token restriction is tacked on without explaining what an agent should do instead when it applies.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with full schema coverage and no output schema, the description covers scope and access restrictions adequately. It is incomplete on how to disambiguate from the many similar task-listing siblings and on result ordering, which matter for correct tool selection in this crowded namespace.

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%, so both parameters (limit and workspace_id) are already fully documented, including defaults and the 'omit = all workspaces' semantics. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource ('Obtiene las tasks completadas') and narrows the scope to the authenticated user's own tasks, which distinguishes it from a general task listing. It stops short of explicitly differentiating from siblings like get_tasks or get_board_tasks, so it lands at 4 rather than 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?

There is no guidance on when to choose this tool over the many sibling task-retrieval tools (get_tasks, get_declared_tasks, get_board_tasks, get_entity_tasks). The only usage-adjacent information is a restriction ('no disponible para tokens sb_*'), which describes a limitation rather than a when-to-use rule.

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