Skip to main content
Glama

get_entity_tasks

Read-onlyIdempotent

Las tareas de una entidad del Atlas: todo lo que está etiquetado con esa persona, proyecto u organización.

Cuenta la entidad en CUALQUIER lugar de `related_entities` (people, projects,
organizations, clients, tags…) y también como responsable. Abiertas primero
(en curso, después pendientes por vencimiento), después las cerradas. Los
nombres de las entidades relacionadas salen con su nombre vigente.
Es la forma corta de "¿qué hay de Acme?" cuando no hay un tablero armado.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMáximo (default: 50)
entity_idYesID de la entidad
entity_typeNoIgnorado: se busca en todas las claves. Queda por compatibilidad
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo
solo_abiertasNotrue = sólo pendientes y en curso (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, yet the description still adds real behavioral substance: the entity is matched anywhere inside related_entities (people, projects, organizations, clients, tags) and as assignee, results are ordered open-first (in-progress, then pending by due date) followed by closed, and related entity names are resolved to their current name.

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 purpose, then matching scope, then ordering, then the routing hint — a sensible sequence. A few sentences (such as the note on current entity names) are detail rather than essential selection information, keeping it just short of maximally tight.

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?

For a five-parameter read tool with no output schema, the description covers matching semantics, sort order and name resolution, which is enough to call it correctly. It leaves the returned shape and truncation behavior implied rather than stated, a minor gap given that limit and workspace handling live in the schema.

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 description coverage is 100%, including the note that entity_type is ignored, so the schema already carries the parameter burden. The description adds only indirect context — that matching spans every related_entities key explains why entity_type is ignored — without documenting limit, workspace_id or solo_abiertas beyond what the schema says.

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 (tasks of an Atlas entity) and immediately defines scope: everything tagged with that person, project or organization, plus items where they are the assignee. The closing line distinguishes it from board-driven views ("la forma corta de '¿qué hay de Acme?' cuando no hay un tablero armado"), so an agent can separate it from get_board_tasks without opening either schema.

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

Usage Guidelines4/5

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

Gives a concrete usage situation — answering "what's going on with Acme?" when no board has been set up — which implies the board-based alternatives are for the other case. It stops short of explicitly naming and excluding sibling tools, so the routing decision is clear in context but not fully spelled out.

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