Skip to main content
Glama
Sign In

TaScan

by io.github.snowbikemike
OverviewDiscussionsAdmin

tascan_list_workers

Read-onlyIdempotent

List workers (taskees) in the organization. Supports filtering by name/email/phone substring, contact-info presence, and last-activity date. Each row includes completion_count (total task completions).

Input Schema

NameRequiredDescriptionDefault
queryNoSubstring match on name, email, or phone
has_emailNotrue/false — same for email
has_phoneNotrue = only workers with a phone on file; false = only without
actor_kindNoOnly these kinds of worker row: person, agent, admin or device, or a comma list (e.g. "person,agent")
active_sinceNoISO date/datetime — only workers with last_active_at on/after this
include_inactiveNotrue = also include inactive workers (e.g. tombstones left by a merge or delete) — useful for auditing right after tascan_merge_workers / tascan_delete_worker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / actor_kind
      Added value: +{
+  "description": "Only these kinds of worker row: person, agent, admin or device, or a comma list (e.g. \"person,agent\")",
+  "type": "string"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / active_since
      Added value: +{
+  "description": "ISO date/datetime — only workers with last_active_at on/after this",
+  "type": "string"
+}
    • addedInput schema / properties / has_email
      Added value: +{
+  "description": "true/false — same for email",
+  "type": "boolean"
+}
    • addedInput schema / properties / has_phone
      Added value: +{
+  "description": "true = only workers with a phone on file; false = only without",
+  "type": "boolean"
+}
    • addedInput schema / properties / include_inactive
      Added value: +{
+  "description": "true = also include inactive workers (e.g. tombstones left by a merge or delete) — useful for auditing right after tascan_merge_workers / tascan_delete_worker",
+  "type": "boolean"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Substring match on name, email, or phone",
+  "type": "string"
+}
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that each row includes completion_count, which is useful return-shape context, but says nothing about pagination, result caps, or ordering — so it adds only modest value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then filtering and result-shape details. Zero wasted text.

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?

No output schema, but the description compensates partially by naming the completion_count return field. Combined with full schema coverage and complete annotations, an agent has what it needs; only pagination/limits are unaddressed, which is a minor gap.

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 parameter meanings are already fully documented in the schema. The description only echoes the filter categories (name/email/phone, contact presence, last activity) without adding syntax or semantics beyond that, so baseline 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?

States a specific verb and resource ('List workers (taskees) in the organization') and clarifies the 'taskees' synonym, which is genuinely useful. It does not distinguish itself from siblings like tascan_get_worker (single lookup) or tascan_list_agents, so sibling differentiation is missing.

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?

The description implies usage by listing supported filters (substring, contact-info presence, last-activity date), which gives an agent a sense of scope. But it never states when to use this vs tascan_get_worker or tascan_list_agents, and gives no exclusions or prerequisites.

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

All TaScan toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources