Skip to main content
Glama

Get the daily draft

standcast_get_draft
Read-onlyIdempotent

Builds yesterday's standup draft from GitHub, Linear and local AI sessions into grouped work items with source warnings, as a starting point you review and confirm before posting.

Instructions

Builds the draft of yesterday's work from the person's GitHub and Linear activity and, unless includeSessions is false, the person's local AI sessions (Claude Code), read on this machine and never sent to Standcast. work groups activity and sessions into work items: build yesterday as a short summary of at most 5 lines, grouping related work items by project or theme. plan (the previous daily's plan against what moved) and pending (the person's open pull requests, review requests and cards) are only for the person; plan is never copied into the daily. warnings names sources that were unavailable. Use it as a starting point: the person decides what goes in the daily.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "standcast_get_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization login. Optional when the person belongs to a single organization.
includeSessionsNoRead the person's local AI sessions into work. Set to false when the person asks not to use their sessions.

Output Schema

NameRequiredDescriptionDefault
orgYes
dateYes
planNo
workNo
sinceYes
teamsYes
pendingNo
activityYes
warningsNo
untrustedYes
suggestionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses substantial behavior: local AI sessions are read on this machine and never sent to Standcast, sessions can be excluded via a flag, output is grouped into work items with a five-line cap, and 'warnings' names unavailable sources. It also clarifies that plan is never copied into the daily, which an agent cannot derive from annotations or schema.

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

Conciseness3/5

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

The first sentence is very long and stacks multiple clauses in nested parentheses, which impedes scanning. More importantly, a large share of the text explains return fields (build, plan, pending, warnings) that the output schema already defines, so the description is carrying redundant weight rather than front-loading the call-critical facts.

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?

The description covers what is needed to call correctly, including the privacy posture of local sessions and when to disable them. Since an output schema exists, the field-by-field explanations are a bonus rather than a requirement, and no essential call-time information appears to be missing.

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 meaningfully expands includeSessions by stating that setting it false suppresses the local-session read entirely and explaining what those sessions are. The org parameter is left to the schema, which is acceptable given the schema already documents it well.

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 pairs a specific verb and resource ('Builds the draft of yesterday's work') and enumerates the input sources (GitHub, Linear, local AI sessions) plus the draft shape. It does not explicitly name a sibling to contrast with, so an agent must infer that this is the pre-composition draft rather than the digest or submit tool, but the intent is unambiguous once the body is read.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it as a starting point: the person decides what goes in the daily' frames the intended moment of use, and 'Set to false when the person asks not to use their sessions' gives a concrete conditional trigger. There are no explicit exclusions or named alternatives, so the routing between this and sibling tools is only implied.

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