Skip to main content
Glama
Sign In

Weft

by com.letsweft
OverviewDiscussionsAdmin

Get Board Briefing

get_board_state
Read-only

Use this when the user asks 'what's on my board?', 'what am I working on?', or any question that needs the shape of the whole board. By default returns a digest: how many tasks there are, the columns and their counts, projects, the active sprint, everything currently in Doing, what is overdue, what is next in Todo, and what closed recently — enough to answer most questions in a fraction of the context. Drill down with list_tasks (by column, sprint or project) or search; use detail:'full' only when you genuinely need every field of every task, which on a large board can exceed a client's response limit.

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": "get_board_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoHow much to return. 'digest' (default) is a briefing about the board; 'full' is every field of every task, capped at 200 tasks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive, so the description correctly focuses on behavior beyond safety: it discloses the context-cost tradeoff and the concrete failure mode that detail:'full' can exceed a client's response limit on a large board. It stops short of describing auth needs or pagination, but the risk disclosure is genuinely actionable.

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

Conciseness4/5

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

Front-loaded with the trigger condition, then the payload contents, then the escape hatches. The digest enumeration is somewhat dense but every item is decision-relevant; no filler sentences.

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?

There is no output schema, so the description carries the return-shape burden — and it does so by listing the digest's contents and warning about the 'full' cap. An agent has everything needed to call this correctly and interpret the result.

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 would be 3, but the description adds decision-relevant meaning: it explains what the 'digest' value actually yields and why 'full' should be reserved, rather than restating the enum labels.

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 ('returns a digest' of 'the shape of the whole board') and enumerates what the digest contains (counts, columns, projects, active sprint, Doing, overdue, next in Todo, recently closed). It is clearly distinguishable from siblings like list_tasks, search, and get_my_work.

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?

Opens with explicit trigger phrases ('what's on my board?', 'what am I working on?'), names the alternatives for drilling down (list_tasks by column, sprint or project; search), and states exactly when detail:'full' is warranted versus overkill.

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

All Weft toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources