THE COOP

Search THE COOP

search

Read-onlyIdempotent

Search published THE COOP articles, approved glossary terms, provider and media profiles and industry events by meaning and keywords. Use for questions and discovery; use search_providers for a name/category directory browse. Returns relevance-ranked results, one passage per record with slug, canonical URL, dates and match_strength (text relevance, not answer confidence). Limited to the top matches, without pagination; empty results mean no matches. Use get_article / explain_term / get_provider / get_event to check full records and sources.

Input Schema

Name	Required	Description
`limit`	No	Maximum distinct records, from 1 to 20 (default 8). Returns the top relevance-ranked matches; no page parameter or exhaustive total.
`query`	Yes	Natural-language question or keywords, e.g. "payment orchestration for UK operators"
`topic`	No	Match this article topic exactly; also set types to ["article"]. Combining with provider filters yields no matches.
`types`	No	Record types to search. provider is canonical; supplier is a deprecated alias. Omit or pass an empty array for all enabled types. Filters combine with AND; a filter for one record type excludes other types.
`review_status`	No	Restrict to provider/media profiles with this review status; also set types to ["provider"]. desk-reviewed means editorially reviewed, not independent verification of every fact; research-candidate means awaiting that review.
`provider_category`	No	Exact provider category; set types to ["provider"].
`supplier_category`	No	Deprecated alias of provider_category; if both are supplied they must match. Match this provider category exactly; also set types to ["provider"]. Use media for publication profiles; combine with review_status to narrow further.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 29, 2026

addedInput schema / properties / provider_category

Added value: +{
+  "description": "Exact provider category; set types to [\"provider\"].",
+  "enum": [
+    "payment-service-provider",
+    "payment-orchestration",
+    "payment-method",
+    "crypto-payments",
+    "platform",
+    "identity-and-compliance",
+    "banking",
+    "legal-and-licensing",
+    "media",
+    "other",
+    "unclassified",
+    "affiliate-and-marketing",
+    "affiliate-software",
+    "analytics-and-data",
+    "casino-game-content",
+    "crm-retention",
+    "crypto-infrastructure",
+    "fraud-and-risk",
+    "game-aggregation",
+    "land-based-gaming",
+    "lottery",
+    "payment-infrastructure",
+    "services-and-consulting",
+    "sportsbook-and-odds"
+  ],
+  "type": "string"
+}

changedInput schema / properties / review_status / description

Previous value: -"Restrict to provider/media profiles with this review status; also set types to [\"supplier\"]. desk-reviewed means editorially reviewed, not independent verification of every fact; research-candidate means awaiting that review."New value: +"Restrict to provider/media profiles with this review status; also set types to [\"provider\"]. desk-reviewed means editorially reviewed, not independent verification of every fact; research-candidate means awaiting that review."

changedInput schema / properties / supplier_category / description

Previous value: -"Match this provider category exactly; also set types to [\"supplier\"]. Use media for publication profiles; combine with review_status to narrow further."New value: +"Deprecated alias of provider_category; if both are supplied they must match. Match this provider category exactly; also set types to [\"provider\"]. Use media for publication profiles; combine with review_status to narrow further."

changedInput schema / properties / types / description

Previous value: -"Record types to search. Omit or pass an empty array for all enabled types. Filters combine with AND; a filter for one record type excludes other types."New value: +"Record types to search. provider is canonical; supplier is a deprecated alias. Omit or pass an empty array for all enabled types. Filters combine with AND; a filter for one record type excludes other types."

changedInput schema / properties / types / items / enum

Previous value: -[
-  "article",
-  "supplier",
-  "event"
-]New value: +[
+  "article",
+  "glossary",
+  "event",
+  "provider",
+  "supplier"
+]

changedInput schema / properties / types / maxItems
```
Previous value: -3New value: +5
```

Changed5 schema fields changedOct 28, 2026

addedInput schema / properties / limit / description

Added value: +"Maximum distinct records, from 1 to 20 (default 8). Returns the top relevance-ranked matches; no page parameter or exhaustive total."

changedInput schema / properties / review_status / description

Previous value: -"Restrict provider results by editorial review status"New value: +"Restrict to provider/media profiles with this review status; also set types to [\"supplier\"]. desk-reviewed means editorially reviewed, not independent verification of every fact; research-candidate means awaiting that review."

addedInput schema / properties / supplier_category / description

Added value: +"Match this provider category exactly; also set types to [\"supplier\"]. Use media for publication profiles; combine with review_status to narrow further."

changedInput schema / properties / topic / description

Previous value: -"Article topic filter"New value: +"Match this article topic exactly; also set types to [\"article\"]. Combining with provider filters yields no matches."

changedInput schema / properties / types / description

Previous value: -"Restrict to record types"New value: +"Record types to search. Omit or pass an empty array for all enabled types. Filters combine with AND; a filter for one record type excludes other types."

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / review_status / description

Previous value: -"Restrict supplier results by editorial review status"New value: +"Restrict provider results by editorial review status"

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / supplier_category / enum

Previous value: -[
-  "payment-service-provider",
-  "payment-orchestration",
-  "payment-method",
-  "crypto-payments",
-  "platform",
-  "identity-and-compliance",
-  "banking",
-  "legal-and-licensing",
-  "media",
-  "other",
-  "unclassified"
-]New value: +[
+  "payment-service-provider",
+  "payment-orchestration",
+  "payment-method",
+  "crypto-payments",
+  "platform",
+  "identity-and-compliance",
+  "banking",
+  "legal-and-licensing",
+  "media",
+  "other",
+  "unclassified",
+  "affiliate-and-marketing",
+  "affiliate-software",
+  "analytics-and-data",
+  "casino-game-content",
+  "crm-retention",
+  "crypto-infrastructure",
+  "fraud-and-risk",
+  "game-aggregation",
+  "land-based-gaming",
+  "lottery",
+  "payment-infrastructure",
+  "services-and-consulting",
+  "sportsbook-and-odds"
+]

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / review_status

Added value: +{
+  "description": "Restrict supplier results by editorial review status",
+  "enum": [
+    "desk-reviewed",
+    "research-candidate"
+  ],
+  "type": "string"
+}

changedInput schema / properties / supplier_category / enum

Previous value: -[
-  "payment-service-provider",
-  "payment-orchestration",
-  "payment-method",
-  "crypto-payments",
-  "platform",
-  "identity-and-compliance",
-  "banking",
-  "media",
-  "other",
-  "unclassified"
-]New value: +[
+  "payment-service-provider",
+  "payment-orchestration",
+  "payment-method",
+  "crypto-payments",
+  "platform",
+  "identity-and-compliance",
+  "banking",
+  "legal-and-licensing",
+  "media",
+  "other",
+  "unclassified"
+]

Changed2 schema fields changedOct 2, 2026

removedInput schema / properties / review_status

Removed value: -{
-  "description": "Restrict supplier results by editorial review status",
-  "enum": [
-    "desk-reviewed",
-    "research-candidate"
-  ],
-  "type": "string"
-}

changedInput schema / properties / supplier_category / enum

Previous value: -[
-  "payment-service-provider",
-  "payment-orchestration",
-  "payment-method",
-  "crypto-payments",
-  "platform",
-  "identity-and-compliance",
-  "banking",
-  "legal-and-licensing",
-  "other",
-  "unclassified"
-]New value: +[
+  "payment-service-provider",
+  "payment-orchestration",
+  "payment-method",
+  "crypto-payments",
+  "platform",
+  "identity-and-compliance",
+  "banking",
+  "media",
+  "other",
+  "unclassified"
+]

First observedOct 2, 2026

TDQS

A4.7/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, closed-world), and the description adds substantive behavior the annotations cannot: relevance-ranked output, one passage per record, slug/URL/dates, no pagination and top-N only, and that match_strength is text relevance rather than answer confidence. The empty-results-means-no-matches clarification removes a common false-negative misread.

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?

Three sentences, front-loaded with capability, then routing, then return-shape caveats. No restatement of the title and no filler; each clause carries distinct information.

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 7-parameter tool with four enums and no output schema, the description closes the gaps an agent would otherwise guess at: result shape, ranking basis, absence of pagination, and the meaning of empty results. No return-value documentation is required elsewhere because it is stated here.

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?

Schema description coverage is 100%, so the schema already documents every parameter, including the AND-combination rules and the topic/provider cross-filter caveat. The description adds little parameter-level detail beyond the no-pagination limit note, so the baseline of 3 applies even though the schema itself is strong.

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 (search) over explicitly enumerated resources (published articles, approved glossary terms, provider/media profiles, industry events) and the retrieval mode (semantic + keyword). It also names the sibling it is not — search_providers for directory browsing — so an agent can route between them without opening either schema.

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?

Gives explicit when-to-use ("questions and discovery") and an explicit alternative with its condition ("use search_providers for a name/category directory browse"). It further routes follow-up work to get_article / explain_term / get_provider / get_event for full records and sources, leaving nothing to inference.

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

All THE COOP tools Inspect

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

Need Help?