THE COOP

Search providers

search_providers

Read-onlyIdempotent

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`page`	No	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.
`limit`	No	Records per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches.
`query`	No	Case-insensitive substring in name or summary; omit to browse.
`category`	No	Exact provider category; media selects publication profiles.
`review_status`	No	Editorial review status, not independent claim verification.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With annotations already covering read-only, idempotent, non-destructive, and closed-world behavior, the description adds useful behavioral detail: results are paginated and ordered by desk-reviewed first, then alphabetically. It does not describe auth or rate limits, but the added ordering and pagination context is meaningful.

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 short sentences, front-loaded with the core purpose, followed by ordering/pagination detail and the key alternative. No wasted wording.

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 5-parameter optional search tool with full schema coverage and complete annotations, the description supplies the missing behavioral context: what is browsed, how results are ordered, that pagination exists, and when to prefer get_provider. Nothing essential is left unclear.

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 page, limit, query, category, and review_status are already well documented in the schema. The description only restates that browsing can be filtered by name, category, and review status, adding little beyond what structured fields provide.

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 gives a specific verb ('Browse'), resource ('published provider and media profiles'), and filtering dimensions ('name, category and review status'). It also explicitly distinguishes this tool from the sibling get_provider by saying to use that tool for sourced facts.

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?

It gives clear usage context: browse published profiles by name/category/status, and use get_provider for sourced facts. It also notes that media profiles are not rated as providers. However, it does not explicitly distinguish this tool from other siblings such as search or search_suppliers.

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?