Skip to main content
Glama
Sign In

FeatureOS

by io.github.featureos
OverviewDiscussionsAdmin

List buckets

list_buckets
Read-only

List all buckets (boards) in the organization.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1).
sortNoOrder results — 'desc' (default), 'asc' (alphabetical ascending), or a time order: 'latest_created_at', 'oldest_created_at', 'latest_updated_at', 'oldest_updated_at'.desc
privacyNo'public' (default), 'private' for private boards only, or 'archived' for archived boards.public

Output Schema

NameRequiredDescriptionDefault
pageNo
bucketsNo
has_moreNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only the organizational scope (results are confined to the org), which is modest value beyond structured data. It says nothing about pagination behavior or result volume for large orgs.

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?

A single front-loaded sentence with zero filler, and the "(boards)" gloss earns its place by mapping terminology. It is perhaps too terse for a tool with three filtering/sorting parameters, but nothing is wasted.

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 simple read-only list endpoint with a fully documented schema, complete annotations, and an output schema covering return values, the description is nearly sufficient. The one real gap is the unstated consequence of the default privacy=public filter, which could lead an agent to believe it sees every bucket in the org.

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?

Schema coverage is 100% with defaults and enum descriptions for page, sort, and privacy, so the schema carries all parameter meaning. The description's phrase "all buckets" arguably understates that privacy defaults to 'public', excluding private and archived boards, but it does not document that nuance itself. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb plus resource ("List all buckets") and disambiguates the term by equating buckets with boards, which is genuinely useful vocabulary bridging. It does not distinguish this tool from nearby siblings such as list_collections or list_articles, so an agent must infer which listing endpoint fits.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no prerequisites, and no mention of the default privacy filter that silently scopes results to public boards. The only usage signal is the implied "no filters needed" from "all buckets."

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

All FeatureOS 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