Skip to main content
Glama

List team blockers

standcast_list_blockers
Read-onlyIdempotent

List blockers confirmed by a team, newest first, with optional date range and pagination; defaults to the last 90 days when no dates are given.

Instructions

Lists the blockers confirmed by the members of a team, newest first, paginated. Without from and to, covers 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>"
    },
    "name": "standcast_list_blockers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast date, YYYY-MM-DD.
orgNoOrganization login. Optional when the person belongs to a single organization.
fromNoFirst 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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds behavior the annotations cannot: result ordering, pagination, and a 90-day default window when the date pair is omitted. It stops short of mentioning permission requirements or what a page contains, but that is largely covered elsewhere.

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, front-loaded with the core action, then the default-window rule. No filler, no restatement of the title, and every clause carries information an agent needs.

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?

For a read-only paginated list tool with an output schema and fully documented parameters, the description covers action, scope, ordering, paging and the default date window. Only marginal gaps remain, such as behavior when the team name does not match standcast.yml or how org interacts with team lookup.

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 a baseline of 3 applies, but the description earns a bump by documenting the coupled default for from/to (last 90 days when both are absent) — a rule present in neither parameter's schema text. The cursor and org parameters get no additional explanation, consistent with the schema already describing them.

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 ('Lists the blockers') plus scope qualifiers: only blockers 'confirmed by the members of a team', ordered newest first and paginated. That is enough to separate it from standcast_list_dailies and standcast_list_teams, though it never names those siblings explicitly.

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 sentence 'Without from and to, covers the last 90 days' tells the agent the default window, which is real usage guidance. But there is no statement of when to prefer this over the other list tools and no exclusions, so guidance remains implied rather than explicit.

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