Skip to main content
Glama

PRO11 Pro Clubs

Search PRO11 guides

search_guides
Read-onlyIdempotent

Searches PRO11’s EA SPORTS FC 27 Pro Clubs guides (builds, positions, tactics, settings, Playoffs, patch notes, names) and returns titles, summaries and links. Use for questions the other tools don’t cover.

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": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return (default 5).
queryYesWhat to look for, e.g. "best CAM build", "crossplay", "patch notes".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the safety profile is settled. The description adds value the annotations cannot: what actually comes back (titles, summaries, links), which tells the agent to expect lightweight result stubs rather than full guide text. It says nothing about ranking, empty-result behavior, or whether limit caps silently, which keeps it from a 5.

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?

Two sentences, front-loaded with the scope, no filler. The parenthetical content-type list is dense but earns its place by signalling what queries will match; it is the one place the sentence stretches.

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 two-parameter read-only search with a fully documented schema and no output schema, the description supplies both the retrieval scope and the return shape. The only omission that matters operationally is behavior on no matches and how results are ordered.

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%: query has examples and length bounds, limit has range and a default of 5. The description adds no syntax, matching, or ranking semantics beyond what the schema states, so the baseline 3 applies.

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 opens with a concrete verb ('Searches') and a narrowly scoped resource: PRO11's EA SPORTS FC 27 Pro Clubs guides. It further enumerates the indexable content (builds, positions, tactics, settings, Playoffs, patch notes, names) and the return shape, so an agent can predict whether a query will hit. It stops short of a crisp contrast with named siblings such as get_archetype or list_formations, relying instead on a generic catch-all clause.

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?

'Use for questions the other tools don't cover' gives a routing rule, but it is a pure fallback framing with no explicit when-not conditions and no named alternative. An agent knows this is the catch-all, but not where the boundary sits relative to structured lookups like get_archetype or list_formations, so it may over- or under-use search.

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