Skip to main content
Glama
AgenticMail

AgenticMail

Official
by agenticmail

check_tasks

Retrieve pending tasks assigned to you or a specific agent, or tasks you assigned to others, filtering by incoming or outgoing direction.

Instructions

Check for pending tasks assigned to you (or a specific agent) or tasks you assigned to others

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

Input Schema

NameRequiredDescriptionDefault
_accountNoOptional. Override identity for THIS call: pass the AgenticMail agent name (e.g. "Fola") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).
assigneeNoCheck tasks for a specific agent by name (only for incoming direction)
directionNoincoming (assigned to me) or outgoing (I assigned)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.104
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.9.101
  3. Removedv0.9.89
  4. Addedv0.9.73
  5. Removedv0.9.69
  6. Addedv0.9.35
  7. Removedv0.9.31
  8. Addedv0.9.12
  9. Removedv0.9.11
  10. Changed1 schema field changedv0.5.63
    • addedInput schema / properties / _account
      Added value: +{
      +  "description": "Optional. Override identity for THIS call: pass the AgenticMail agent name (e.g. \"Fola\") to authenticate as that agent. Requires AGENTICMAIL_ACCOUNT_KEYS_JSON to contain a matching key. Omit to use the default identity (AGENTICMAIL_API_KEY).",
      +  "type": "string"
      +}
  11. First observedv0.5.59

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it does not say this is a read-only operation, whether results are paginated, whether completed tasks are excluded by 'pending', or what authentication identity applies. The only behavioral hint is the parenthetical that the assignee lookup is for a specific agent, which is already in the schema. For an unannotated tool this leaves too much undisclosed.

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 front-loaded sentence with no filler; the two query shapes are expressed compactly. The nested parentheses make it slightly denser to parse than necessary, but nothing is wasted.

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?

Three optional parameters and no output schema mean the description should clarify what a 'pending task' record looks like and how it is scoped, and it does not. It is adequate to select and call the tool with the right direction, but not to predict the response.

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%, so the schema already documents _account, assignee, and the incoming/outgoing enum. The description restates the direction semantics in prose but adds no syntax, defaults, or constraints beyond the schema — and notably omits the schema's restriction that assignee applies only to the incoming direction.

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 ('check') and resource ('tasks') and scopes it to two modes: tasks assigned to the caller (or a named agent) versus tasks the caller assigned to others. That maps cleanly onto the incoming/outgoing axis, so an agent can tell what the tool returns. It does not name a sibling such as claim_task, so it stops short of full differentiation.

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?

Usage is implied by 'pending tasks' — you call this to see outstanding work — and the direction phrasing hints at the two query modes. There is no explicit when-not guidance and no mention of claim_task as the alternative for acting on a task rather than listing one.

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