Skip to main content
Glama

List Organizations

sirv_list_organizations
Read-onlyIdempotent

Lists the workspaces the signed-in user belongs to and returns each organization’s ID and role, so you can pass the correct orgId to library, product, Shopify, Supplier Portal, and Sirv file tools.

Instructions

List the workspaces (organizations) that the signed-in user belongs to.

Use it when the user names another workspace: pass its id as orgId to the library, product, Shopify, Supplier Portal and Sirv file tools. Without orgId, those tools use the workspace you signed in to. It takes no inputs.

Read-only. Returns each workspace's id, name, slug, the user's role, and whether it is a personal workspace and whether the user owns it.

Credits: free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds context beyond them: it is input-free, enumerates the returned fields (id, name, slug, role, personal flag, ownership flag), and notes the operation costs no credits. That return-shape disclosure matters because no output schema exists.

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?

Four short paragraphs ordered by usefulness: what it lists, when to reach for it, what it returns, and cost. Every sentence carries distinct information with no repetition of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter read tool with no output schema, the description supplies everything an agent needs: purpose, the orgId hand-off pattern, the exact return fields, and the cost. Nothing material is left to inference.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the schema to document and none is needed. The description's explanation of orgId adds meaning, but orgId belongs to the sibling tools rather than to this one, so it is guidance rather than this tool's parameter semantics.

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 ('List the workspaces (organizations) that the signed-in user belongs to') and disambiguates the parenthetical synonym. No sibling tool in the catalog lists organizations, so an agent can identify the target immediately.

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

Usage Guidelines5/5

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

Explicitly names the triggering condition ('when the user names another workspace') and the follow-on action (pass its id as orgId to the library, product, Shopify, Supplier Portal and Sirv file tools). It also states the default behavior absent orgId, so the agent understands both branches.

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