Skip to main content
Glama
Sign In

Antwork

by io.antwork
OverviewDiscussionsAdmin

list_workspaces

Read-only

The user's workspaces, their Antwork account (plan, post quota), and the active workspace's connected accounts.

isDefault marks the workspace every tool uses when workspace_id is omitted. isOwner: false is a workspace the user was invited to; its owner pays for its accounts. account.quota.posts.remaining is what the plan still allows this cycle.

account.billing.billingUrl is the page where the plan is changed or cancelled. foundingOffer is a discount (percentOff off the first year of a yearly plan) that ends at endsAt; unlimitedPostsUntil is the date after which Free allows postsPerMonthAfter posts a month. A comped account is free and has nothing to change. account.trialNotice appears in a trial's last days and the week after: state (ending or ended), the plan tried, endsAt, and free, what the Free plan keeps.

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

Input Schema

NameRequiredDescriptionDefault
contextNoThe user's underlying goal for this call, in one sentence without personal details. Used for product analytics only.
llm_modelNoThe model identifier of the calling assistant, or "unknown". Used for product analytics only.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
-  "context",
-  "llm_model"
-]New value: +[]
  2. 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 free. The description adds useful interpretation of payload values (isOwner means someone else pays; comped accounts are free with nothing to change; trialNotice timing), but says nothing about auth requirements, rate limits, or pagination, and much of the field detail likely duplicates the output schema.

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

Conciseness3/5

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

The lead sentence is well front-loaded, but the remainder is a dense, backtick-heavy glossary of return fields that reads like reference documentation rather than invocation aid. Each fact is individually useful, yet the density makes it hard to scan for the decision-relevant content.

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 read-only listing tool with a full output schema and 100% parameter coverage, the description supplies plenty of domain model (ownership, billing, quota, trial states). What it lacks is the one thing an agent most needs when several listing tools exist: how this differs from list_social_accounts and when to prefer each.

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?

All three parameters (context, llm_model, conversation_id) have full schema descriptions, so the schema carries the burden; baseline 3 applies. The prose description adds no meaning about any parameter, and notably does not reinforce the conversation_id continuity rule that the schema states.

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 opening sentence names three concrete resources returned: the user's workspaces, the Antwork account (plan, post quota), and the active workspace's connected accounts. That is specific enough to distinguish it from most siblings, though it overlaps with list_social_accounts on 'connected accounts' without clarifying the difference.

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 explicit when-to-use or when-not-to-use guidance and no alternative named. The only routing-adjacent content is the note that `isDefault` marks the workspace other tools use when `workspace_id` is omitted, which is cross-tool semantics rather than a selection rule for this tool.

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

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