Skip to main content
Glama

arr_search_all

Read-only

Search all configured *arr services at once by term to find movies, shows, music, and books from a single query.

Instructions

Search across all configured *arr services for any media

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "arr_search_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesSearch term

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-reach profile is covered. The description adds only that the search fans out across every configured service; it says nothing about how partial failures on one service are handled, result ordering/merging, or volume of results returned.

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?

One short sentence, front-loaded with the verb and scope, with no filler. It is efficient, though so terse that useful details (aggregation behavior, alternatives) were dropped rather than condensed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read-only search with full schema coverage and no output schema, the description is adequate but thin: it omits what the aggregated results look like and how per-service errors surface. An agent can call it correctly, but not predict its output shape or failure modes.

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 there is a single 'term' string parameter already documented in the schema. The description adds no meaning beyond that — no note on matching semantics, whether it accepts IDs or titles, or per-media-type query formats.

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 states a specific verb and resource ('Search ... for any media') and scopes it to 'all configured *arr services', which implicitly separates it from the per-service siblings such as radarr_search or sonarr_search. It never names those alternatives explicitly, so the differentiation is inferable rather than stated.

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?

'Across all configured *arr services' hints at the use case (broad, cross-service lookup) versus narrower sibling searches, but there is no explicit when-to-use/when-not-to-use guidance and no mention of credential or configuration prerequisites. An agent must infer the routing decision from the word 'all'.

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

Deploy Server

Other Tools