Skip to main content
Glama

List team dailies

standcast_list_dailies
Read-onlyIdempotent

Lists a team's confirmed dailies between two dates, newest first and paginated, so you can review standup history within the last 90 days.

Instructions

Lists the confirmed dailies of a team between two dates, newest first, paginated. Limited to the last 90 days.

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": {
      "team": "<team>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "standcast_list_dailies"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesLast date, YYYY-MM-DD.
orgNoOrganization login. Optional when the person belongs to a single organization.
fromYesFirst date, YYYY-MM-DD.
teamYesTeam name as written in standcast.yml.
cursorNonext_cursor of the previous page.

Output Schema

NameRequiredDescriptionDefault
dataYes
untrustedYes
next_cursorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 openWorldHint=false, so safety is covered structurally. The description adds genuinely new behavior: results are newest-first, results are paginated, and retrieval is capped at the last 90 days, which tells the agent a valid 'from' outside that window will yield nothing.

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 short sentences with zero filler. The core action and scope come first, followed by ordering, pagination and the retention limit — exactly the order an agent needs to decide and then call.

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?

With an output schema present, the description need not describe return values, and annotations cover the safety profile. What it discloses — scope, ordering, pagination and the 90-day cap — is close to complete, with only minor gaps such as date-bound inclusivity and whether the 90-day cap is measured from today.

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 baseline is 3; team, from, to, org and cursor are already documented in the schema. The description only lightly reinforces this by saying 'between two dates' and 'paginated', without clarifying inclusive/exclusive date bounds or how the cursor interacts with ordering.

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 gives a specific verb ('Lists') tied to a precisely scoped resource ('confirmed dailies of a team'), and adds the qualifier 'confirmed' plus ordering and pagination. It is clearly distinct from siblings like standcast_list_blockers or standcast_list_teams, though it does not name an alternative to route against.

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 rather than stated: an agent can infer it should call this when it needs dailies for a specific team within a date window. The 90-day retention limit is the one explicit constraint, but there is no guidance on when to prefer a different tool (e.g., standcast_get_digest) or prerequisites such as org resolution.

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