Skip to main content
Glama
Sign In

Syndicate

by trade.syndicate
OverviewDiscussionsAdmin

List syndicates

list_syndicates
Read-onlyIdempotent

Browse public syndicates (shared trading books run by operators), newest first: id, name, pitch, emblem, status, operators and member count. Page with cursor.

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_syndicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-50 (default 20).
cursorNo`next_cursor` from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 openWorld, so the safety profile is covered. The description adds behavior beyond that: results are limited to public syndicates, ordering is newest-first, and paging is driven by a cursor. It does not mention total counts or rate limits, which keeps it short of a 5.

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 tight sentences: the primary behavior and returned fields come first, followed by a short paging instruction. There is no filler and the ordering constraint is front-loaded.

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 paginated list with full annotation coverage and no output schema, enumerating the returned fields (id, name, pitch, emblem, status, operators, member count) compensates well for the missing output schema. Only total-count or page-boundary behavior is left unspecified, which is a minor gap.

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% and both parameters are already documented, including the default and range for limit and the meaning of cursor. The description only says 'Page with cursor', which restates rather than extends the schema, so baseline 3 applies.

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?

The description gives a specific verb-plus-resource ('Browse public syndicates'), defines the domain term ('shared trading books run by operators'), and adds distinguishing characteristics (public-only, newest first) that separate it from the singular sibling get_syndicate.

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?

Usage is implied by 'Browse' and 'public', and the pagination sentence hints at multi-page retrieval, but it never states when to use this versus get_syndicate or search-style siblings, nor any exclusions.

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

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