Skip to main content
Glama
Sign In
musterd

musterd

Official
by musterd-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

team_seed_list

Lists shared Team Seeds awaiting exploration, showing active work by default and including completed or promoted history when requested.

Instructions

List shared Team ideas waiting for exploration. The default active tray includes work in progress and recently completed Seeds; history:true includes every Seed.

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

Input Schema

NameRequiredDescriptionDefault
historyNoinclude completed and promoted history

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description must carry the behavioral load. It does disclose scope boundaries — what the default tray contains (work in progress and recently completed) versus history (every Seed) — but says nothing about ordering, result limits, or whether access to other members' Seeds requires anything special.

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 sentences, zero filler, with the default behavior front-loaded before the flag variant. Every clause conveys scope information the 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 one-optional-parameter read tool with no output schema, the description covers purpose and both modes adequately. Minor gaps in result ordering or volume are low-stakes here.

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?

The single parameter is fully documented in the schema (100% coverage), and the description adds a meaningful gloss by framing history as 'every Seed' rather than only completed/promoted items. That is a modest clarification beyond the schema wording, so baseline 3 is right.

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 — 'List shared Team ideas waiting for exploration' — and clarifies the item type is 'Seeds', which lets an agent distinguish it from singular siblings like team_seed_get. It stops short of explicitly differentiating from other list-style siblings such as lane_board or team_insight_search.

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?

Explains the two operating modes: the default 'active tray' and the 'history:true' variant, which tells the agent which mode to pick for current work vs. full archive. It offers no explicit exclusions or pointer to the sibling that fetches a single Seed.

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

Deploy Server

Other Tools