Skip to main content
Glama

Opencollective

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Transactions

transactions
Read-onlyIdempotent

Transaction list for a collective.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYes
typeNoCREDIT | DEBIT (default both)
limitNo1-1000 (default 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of items returned.
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "slug": "babel"
+  },
+  {
+    "limit": 50,
+    "slug": "webpack",
+    "type": "CREDIT"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of items returned.",
+      "type": "integer"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "amount": {
+            "description": "Amount in cents",
+            "type": "number"
+          },
+          "createdAt": {
+            "description": "Transaction date (ISO 8601)",
+            "type": "string"
+          },
+          "currency": {
+            "description": "Currency code",
+            "type": "string"
+          },
+          "description": {
+            "description": "Transaction description",
+            "type": "string"
+          },
+          "fromCollective": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "id": {
+            "description": "Transaction ID",
+            "type": "string"
+          },
+          "toCollective": {
+            "properties": {
+              "id": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              },
+              "slug": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": {
+            "description": "Transaction type",
+            "enum": [
+              "CREDIT",
+              "DEBIT"
+            ],
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items",
+    "count"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

C2.7/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, so the safety profile is clear. Description adds no extra behavioral context (e.g., pagination, filtering details). Adequate given annotations.

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

Conciseness2/5

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

Extremely short (7 words) but under-specified. Does not meet the bar for conciseness; it lacks necessary detail for a tool with 3 parameters.

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

Completeness2/5

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

Despite having an output schema, the description is too minimal. Does not mention filtering options, pagination, or scope. For a list tool with 3 params, more context is needed.

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 67% (type and limit have descriptions, slug does not). Description adds no information about parameters. Could have explained slug or other constraints to compensate.

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?

Clears verb+resource: 'Transaction list for a collective.' It states it lists transactions for a collective. However, it does not differentiate from sibling tools like 'events' or 'recent_changes', which also list data.

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 vs alternatives. Siblings include other list tools, but no context on when transactions is appropriate.

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