Skip to main content
Glama
Sign In

THE COOP

by media.thecoop
OverviewDiscussionsAdmin

Search suppliers (deprecated)

search_suppliers
Read-onlyIdempotent

Deprecated alias of search_providers. Browse published provider and media profiles by name, category and review status. Results are paginated, desk-reviewed first and then alphabetical. Use get_provider for sourced facts; media profiles are not rated as providers.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1 (default 1, maximum 500). Keep filters and limit unchanged while paging; stop at total_pages. A page beyond the results returns an empty items array.
limitNoRecords per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches.
queryNoCase-insensitive substring in name or summary; omit to browse.
categoryNoExact provider category; media selects publication profiles.
review_statusNoEditorial review status, not independent claim verification.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Match this category exactly. Omit for all categories; media selects publication profiles."New value: +"Exact provider category; media selects publication profiles."
    • changedInput schema / properties / query / description
      Previous value: -"Case-insensitive substring in the name or summary, up to 200 characters. Omit or leave empty to browse; this is not semantic search."New value: +"Case-insensitive substring in name or summary; omit to browse."
    • changedInput schema / properties / review_status / description
      Previous value: -"Match editorial review status: desk-reviewed for reviewed profiles, research-candidate for profiles awaiting review. Omit for both; this is not a claim-verification filter."New value: +"Editorial review status, not independent claim verification."
  2. Changed5 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Match this category exactly. Omit for all categories; media selects publication profiles."
    • addedInput schema / properties / limit / description
      Added value: +"Records per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches."
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1 (default 1, maximum 500). Keep filters and limit unchanged while paging; stop at total_pages. A page beyond the results returns an empty items array."
    • changedInput schema / properties / query / description
      Previous value: -"Name or keyword"New value: +"Case-insensitive substring in the name or summary, up to 200 characters. Omit or leave empty to browse; this is not semantic search."
    • addedInput schema / properties / review_status / description
      Added value: +"Match editorial review status: desk-reviewed for reviewed profiles, research-candidate for profiles awaiting review. Omit for both; this is not a claim-verification filter."
  3. Changed1 schema field changed
    • changedInput schema / properties / 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"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / 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"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / 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"
+]
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioural detail: results are paginated and ordered desk-reviewed first, then alphabetically. It stops short of describing response shape (items, total_items, total_pages), which the schema hints at but the description doesn't confirm.

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

Conciseness4/5

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

Four short sentences, front-loaded with the deprecation notice and the alias relationship, then function, then ordering, then routing. Nothing is wasted, though the ordering sentence and the get_provider pointer could be tightened slightly.

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?

For a read-only search with no output schema, the description covers what matters: what is searched, sort order, pagination, and where to go for authoritative detail. The only gap is a clear instruction to use the successor tool rather than this deprecated alias, which is implied but not stated.

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 every parameter (page, limit, query, category, review_status) is already well documented, including paging semantics and the media category special-case. The description only restates the filter surface ('by name, category and review status') without adding syntax or edge-case detail beyond the schema, so baseline 3 applies.

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 first sentence pins the tool's identity precisely: a deprecated alias of search_providers that browses published provider and media profiles. It names the resource (providers/media profiles), the filters (name, category, review status), and distinguishes itself from both search_providers and get_provider.

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 clearly routes agents elsewhere for sourced facts ('Use get_provider for sourced facts') and flags that this is deprecated in favour of search_providers. What it does not say explicitly is 'prefer search_providers instead of calling this tool', leaving the deprecation signal implicit rather than an outright directive.

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

All THE COOP 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