OpenCollective MCP Server

oc_get_members

Read-onlyIdempotent

Retrieve members and backers of an OpenCollective account, including roles, donation totals, and linked account details.

Instructions

List members and backers of an OpenCollective account.

Returns member roles (ADMIN, MEMBER, BACKER, etc.), donation totals, and linked account info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "oc_get_members"
  }
}

Input Schema

Name	Required	Description	Default
`ctx`	No
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 5, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false. The description adds value by specifying the returned data (roles, donations, linked account info) beyond annotations. No contradictions.

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 concise sentences, front-loaded with the main purpose. Every sentence adds value; no unnecessary words.

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?

The description covers the input (account slug) and output (roles, donations, linked info). Annotations provide safety guarantees. Minor gap: pagination (limit/offset) is not mentioned, but it's a listing tool with common parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% per context signal, meaning no parameter descriptions in the schema itself. The description does not explain the parameters (slug, limit, offset) beyond the main purpose, so it fails to compensate for the missing schema descriptions.

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 clearly states 'List members and backers of an OpenCollective account' with a specific verb and resource, and lists what is returned (roles, donations, linked info). It is well-distinguished from sibling tools which are mostly about invoices and expenses.

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

Usage Guidelines4/5

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

The description implies when to use (when you need member/backer info) but does not explicitly state when not to use or provide comparisons to alternatives. However, no sibling tool serves the same purpose, so the context is clear.

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