Skip to main content
Glama

Clients in follow-ups

dosai_list_followups
Read-onlyIdempotent

Clients the bot is currently following up (reminding after they went silent): status, how many touches were sent, when the next one goes.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_list_followups"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, default 1.
limitNoRows per page, max 50, default 20.
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is handled. The description adds real value beyond that by disclosing what the records represent (silent clients being reminded) and what fields come back (status, touch count, next scheduled touch) despite there being no output schema; it omits ordering and whether completed/paused follow-ups are excluded.

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 fragment with no filler; the parenthetical definition is genuinely load-bearing. It loses a point only for being a fragment with no explicit verb, which reads slightly less crisply than a full 'List …' construction.

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?

This is a simple, read-only, single-project paginated list with fully documented parameters, rich annotations and no output schema. The description covers what the resource is, what state qualifies, and what data is returned — everything an agent needs to decide to call it and what to expect back.

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% — page, limit and project_id all carry inline descriptions including defaults and bounds — so the schema does the heavy lifting. The description adds nothing about parameters (not even that project_id scopes the list), which makes the baseline 3 appropriate.

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?

Names a specific resource — clients the bot is currently following up — and even defines the concept inline ("reminding after they went silent"), so the agent knows this is a filtered list of in-progress follow-up targets rather than all contacts. It does not, however, distinguish itself from near-neighbours like dosai_list_followup_steps or dosai_list_lead_reminders, which the agent must infer.

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 "currently following up" — an agent can reason it is for inspecting active follow-up queues — but there is no explicit when-to-use statement, no prerequisites (e.g. a project must exist), and no named alternative for looking at follow-up configuration versus follow-up state.

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