Skip to main content
Glama

FlowCastle

by ai.flowcastle
OverviewDiscussionsAdmin

list_follow_up_tasks

Read-only

List follow-up tasks — reminders for a person to get back to a contact. Read-only, ordered by due time so overdue work comes first. A follow-up sends nothing by itself. Scopes: mine is the open work assigned to the key's owner and needs a personal key; unassigned is unowned open work; team is all open work; completed is closed history. unassigned, team and completed reach past the caller's own tasks ONLY for an owner or admin of the application, or a workspace API key. For any other personal key unassigned and team return the same as mine, and completed returns only their own closed tasks — the result's scope.narrowedToOwn is true when that happened. Without a scope a personal key reads mine and a workspace key reads team. completionReason tells a person closing a task apart from the platform closing it (customer_replied, expired_unanswered).

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Defaults to 1.
limitNoTasks per page, 1-100. Defaults to 20.
scopeNoWhose work to list. `mine` requires a personal API key; `unassigned`, `team` and `completed` widen past the caller's own tasks only for an owner, an admin or a workspace key.
originNoWho created it: a person, the AI analysis, or a deterministic rule.
searchNoSubstring match on the contact's name, username, or platform id.
timingNoNarrow by when the task is due. Omit for all open work.
applicationIdNoApplication (workspace) id. Optional: an application-scoped key (app_...) defaults to its own application, but a personal key (usr_...) has no default and omitting it fails with MCP_APPLICATION_REQUIRED. Call list_applications to get the id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scope / description
      Previous value: -"Whose work to list. `mine` requires a personal API key."New value: +"Whose work to list. `mine` requires a personal API key; `unassigned`, `team` and `completed` widen past the caller's own tasks only for an owner, an admin or a workspace key."
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses that results are ordered by due time so overdue work comes first, that follow-ups do not send messages, and that `scope.narrowedToOwn` signals permission-based narrowing. It also explains `completionReason` semantics, separating human closure from platform closure.

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?

The description is dense and front-loaded, starting with the core purpose and read-only nature before scope details. It is somewhat long as a single paragraph, but nearly every sentence carries useful behavioral or permission context.

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 complex permissioned listing tool with no output schema, the description covers scope behavior, default behavior, narrowing signals, ordering, and completion semantics. An agent has enough information to choose a scope and interpret key edge cases correctly.

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 100%, so the baseline is 3, but the description adds meaningful semantics for `scope`, explaining permission widening, default behavior, and fallback behavior beyond the schema enum. It does not add much for `page`, `limit`, `origin`, `search`, or `timing`, which remain schema-documented only.

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?

The description states a specific verb and resource ("List follow-up tasks") and immediately defines what the resource means: reminders for a person to get back to a contact. It also distinguishes the tool from its create/update siblings through its read-only, listing nature and by explaining that a follow-up sends nothing by itself.

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?

It gives explicit scope-selection guidance for `mine`, `unassigned`, `team`, and `completed`, including the permissions each scope requires and how results narrow for personal keys. It also states the default scope behavior separately for personal and workspace keys, leaving little for an agent to infer.

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

All FlowCastle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources