Skip to main content
Glama

Get a team digest

standcast_get_digest
Read-onlyIdempotent

Retrieve a team's standup digest for a specific date to check who sent the daily and who missed it; returns null when no digest exists. Limited to the last 90 days.

Instructions

Returns the digest delivery of a team on one date, with who had not sent the daily, or null when there is none. 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>",
      "date": "<date>"
    },
    "name": "standcast_get_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization login. Optional when the person belongs to a single organization.
dateYesStandup date, YYYY-MM-DD.
teamYesTeam name as written in standcast.yml.

Output Schema

NameRequiredDescriptionDefault
digestYes
untrustedYes

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 readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description still earns credit by disclosing two things the annotations do not: that a missing digest yields null rather than an error, and that lookups are capped at the last 90 days.

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?

A single sentence, front-loaded with the return value, then the payload content, then the null case, then the scope limit. No redundant or filler wording.

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?

An output schema exists, so return shape need not be described, and the description still covers the empty-result behavior and the 90-day ceiling. Minor gaps remain, such as what happens for an unknown team name, but nothing essential to invoking it correctly is absent.

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%, with org, date, and team each documented including the optional-when-single-org rule and the YYYY-MM-DD pattern. The description adds no parameter meaning beyond that, so the baseline of 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: 'Returns the digest delivery of a team on one date', plus what the payload contains (who had not sent the daily) and the null case. That is concrete enough to separate it from siblings like standcast_list_dailies or standcast_get_draft, though it never explicitly contrasts itself with them.

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 90-day window is a real usage constraint that tells an agent when this call cannot be used, but there is no explicit guidance on when to prefer this over standcast_list_dailies or standcast_get_draft. Usage is only implied by the resource name.

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