Skip to main content
Glama

Find Poacher sources

list_sources
Read-onlyIdempotent

Search the public catalog of sites Poacher can watch. Returns each source’s name, category, status (fixture_available or planned) and current availability. A listed source still needs the exact search checked in the app before anyone pays for monitoring. No sign-in.

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": "list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to match in a source’s name, category or description, for example "rare books" or "eBay". Omit to list every source.

Output Schema

NameRequiredDescriptionDefault
dataNo
noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious context beyond that: no sign-in is required, the catalog is public, and a listed source does not guarantee the exact search is monitored — a caveat an agent would otherwise get wrong.

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?

Four short sentences, front-loaded with the purpose, then return shape, then the important caveat, then the auth note. Nothing is repeated and every sentence carries distinct information.

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?

With an output schema present and full param coverage, the description does not need to explain return values — yet it still names the key fields and the status values, and it covers the auth and verification caveats. The only soft spot is "current availability," which is left undefined given the status enum is only implied.

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 coverage is 100% and the single query parameter already documents matching behavior, examples, the 120-char limit and what happens when omitted. The description only restates that this searches the catalog, adding no new parameter semantics, so the 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 description opens with a specific verb and resource: "Search the public catalog of sites Poacher can watch." It then enumerates what each returned source contains (name, category, status, availability), which makes the tool's scope unambiguous relative to the alert/channel/check siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is a useful workflow caveat — a listed source still requires the exact search to be checked in the app before paying for monitoring — which tells the agent this listing is a discovery step, not a purchase step. However, it never explicitly states when to call this versus other discovery tools (e.g. get_capabilities), so the guidance is implied rather than declared.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources