Skip to main content
Glama

Submit the daily

standcast_submit_daily
Idempotent

Submits your daily standup to the team only after explicit confirmation and replaces any earlier submission for the same day.

Instructions

Submits the person's daily to their teams. Before calling, you MUST show the final daily to the person and get their explicit confirmation. When the client supports elicitation, Standcast also asks the person directly and sends nothing unless they accept. Otherwise, call with confirmed: true only after the person explicitly confirmed. Send each item exactly as the person wrote or approved it: never translate or rewrite it. Submitting again on the same day replaces the previous daily.

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": {
      "yesterday": "<yesterday>",
      "today": "<today>",
      "blockers": "<blockers>"
    },
    "name": "standcast_submit_daily"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNoOrganization login. Optional when the person belongs to a single organization.
todayYesWhat the person will do today.
supportNoWhat the person needs help with from others, without being blocked.
blockersYesWhat is blocking the person.
confirmedNoSet to true only after the person explicitly confirmed this daily. Required when the client does not support elicitation.
yesterdayYesWhat the person did.

Output Schema

NameRequiredDescriptionDefault
dateYes
lateYes
teamsYes
confirmationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true; the description adds real context beyond that: the confirmation gate, the elicitation fallback, and that resubmitting replaces the previous daily. The content-fidelity rule ('never translate or rewrite') is also behavioral guidance not present in structured fields.

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?

Four sentences, each carrying a distinct rule, with the mandatory confirmation requirement front-loaded immediately after the purpose statement. No filler.

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?

Covers the full call contract for a mutating, open-world submit tool: confirmation gating, elicitation behavior, content fidelity, and replacement semantics. An output schema exists, so return values need not be described.

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; the description adds meaning by tying the confirmed flag to the confirmation workflow and by constraining how the text fields must be populated (verbatim as written or approved). It does not explain org or the ref objects, but the schema already does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Submits the person's daily to their teams') and implicitly distinguishes itself from read-oriented siblings like standcast_get_draft and standcast_get_digest by being the write/submit action.

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

Usage Guidelines5/5

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

Gives explicit preconditions: show the final daily and obtain explicit confirmation before calling, use the elicitation path when supported, and otherwise pass confirmed: true only after explicit confirmation. It also states the same-day resubmission behavior, so the agent knows when re-calling is appropriate.

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