Skip to main content
Glama

filters

Free. The values Poseidon accepts, with live counts: niches, Meta formats, countries with reach data, age bands, sort orders, the winner rule and the coverage. Call it when unsure of a niche name or a country code, or when the user asks what Poseidon covers.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: 'Free' signals no cost/credits, 'live counts' signals data freshness rather than a static enum, and the content list implies a read-only lookup. It does not describe the response shape or latency, and 'the winner rule and the coverage' are unexplained terms an agent may not understand.

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?

Two compact sentences, front-loaded with the cost signal 'Free.' followed by content scope and then the call conditions. No filler.

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 zero-parameter lookup with no output schema, the description adequately previews the returned categories. The gaps are minor: 'the winner rule' and 'the coverage' are named but never explained, leaving some return content opaque.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so parameter semantics are not a concern and the baseline for a no-param tool is 4. The description correctly implies no inputs are needed.

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?

The description identifies a reference/enumeration tool and enumerates its contents (niches, Meta formats, countries with reach data, age bands, sort orders, winner rule, coverage). That is specific enough to distinguish it from siblings like search_winners or get_brand, though it opens with the nominal phrase 'The values Poseidon accepts' rather than a clear verb such as 'List'.

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 explicit trigger conditions: call it when unsure of a niche name or country code, or when the user asks what Poseidon covers. It does not state when NOT to use it or name an alternative for resolving names, so it stops short of full routing guidance.

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