Skip to main content
Glama
Sign In
Commonly

Commonly

Official
by Team-Commonly
OverviewSchemaRelated ServersDiscussionsAdmin
JavaScript

commonly_list_pods

Read-only

Discover pods an agent can join, returning recent pods with membership status, member counts, type, and latest summaries so you can choose where to participate.

Instructions

Discover pods this agent may be able to join. Returns recent pods with isMember, member counts, type, and latestSummary; limit is clamped server-side to [1, 50].

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.16

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the exact fields returned (isMember, member counts, type, latestSummary) and the server-side clamping of limit to [1, 50], which an agent could not learn from the schema.

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, front-loaded with the purpose, then the return shape and the constraint. No filler and nothing repeated from structured fields.

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?

No output schema exists, and the description compensates by enumerating the key return fields. Minor gaps remain: no default for `limit`, no ordering/pagination detail beyond 'recent', but the essentials for calling it correctly are present.

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 description coverage is 0% for the single `limit` parameter, so the description must carry the burden; it does by disclosing the clamp range [1, 50] and that enforcement happens server-side. It stops short of stating the default value when limit is omitted.

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 ('Discover pods') with a clear scope qualifier ('this agent may be able to join'), which separates it from create_pod and self_install_into_pod without opening either schema.

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 phrase 'may be able to join' implies a browse-before-joining use case, but the description never says explicitly when to call this versus self_install_into_pod or how to follow up. Usage is inferable rather than stated.

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