Skip to main content
Glama

Opencollective

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Collective

collective
Read-onlyIdempotent

Public collective info by slug (name, balance, currency, sponsors).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYese.g. "babel", "webpack", "preact"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoCollective ID
nameNoCollective display name
slugNoCollective slug identifier
imageNoLogo/image URL
statsNo
balanceNoCurrent balance in cents
twitterNoTwitter handle
websiteNoOfficial website URL
currencyNoCurrency code (e.g. USD)
descriptionNoCollective description
backgroundImageNoBackground image URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "slug": "babel"
+  },
+  {
+    "slug": "webpack"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "backgroundImage": {
+      "description": "Background image URL",
+      "type": "string"
+    },
+    "balance": {
+      "description": "Current balance in cents",
+      "type": "number"
+    },
+    "currency": {
+      "description": "Currency code (e.g. USD)",
+      "type": "string"
+    },
+    "description": {
+      "description": "Collective description",
+      "type": "string"
+    },
+    "id": {
+      "description": "Collective ID",
+      "type": "string"
+    },
+    "image": {
+      "description": "Logo/image URL",
+      "type": "string"
+    },
+    "name": {
+      "description": "Collective display name",
+      "type": "string"
+    },
+    "slug": {
+      "description": "Collective slug identifier",
+      "type": "string"
+    },
+    "stats": {
+      "properties": {
+        "backers": {
+          "description": "Number of backers",
+          "type": "number"
+        },
+        "contributors": {
+          "description": "Number of contributors",
+          "type": "number"
+        },
+        "sponsors": {
+          "description": "Number of sponsors",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "twitter": {
+      "description": "Twitter handle",
+      "type": "string"
+    },
+    "website": {
+      "description": "Official website URL",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that the info is 'public' and lists return fields, which is helpful but does not go beyond what annotations already indicate about safety. The description is consistent with annotations.

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?

One concise sentence with no wasted words. Information is front-loaded: the verb 'info' and resource 'collective' are immediately clear.

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?

Given the single parameter, full schema coverage, annotations, and presence of an output schema (not shown but indicated), the description is complete enough. It specifies the returned fields, which is sufficient for an agent.

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?

The input schema covers the single parameter 'slug' with examples, achieving 100% coverage. The description mentions 'by slug' but does not add further meaning; baseline 3 is appropriate.

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 the action ('get public collective info'), the resource ('collective'), and the method ('by slug'), with explicit fields returned (name, balance, currency, sponsors). It is specific and distinguishes this tool from siblings.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when-not to use, or refer to sibling tools for additional context.

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

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