Skip to main content
Glama

cautare_pacanele

Read-only

Returnează paginile site-ului al căror nume include textul indicat: pagini de jocuri, pagini de studiouri și pagini de colecții. Nu ține cont de tema, subiect sau descriere. Recenzii disponibile: 9

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": {
      "s": "<s>"
    },
    "name": "cautare_pacanele"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesNumele unui joc, al unui studio de jocuri sau al unei colecții ori o parte din acest nume, de minimum două caractere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered by structured data. The description adds value by disclosing the matching rule (name substring only, ignoring theme/subject/description) and the result page types, which annotations cannot convey. It omits ordering, result caps, pagination, and the meaning of the trailing 'Recenzii disponibile: 9', so it is helpful but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are front-loaded and earn their place, defining the verb, the covered page types, and the exclusion. The closing 'Recenzii disponibile: 9' is cryptic and unexplained — it reads as leftover artifact rather than actionable information, diluting an otherwise tight definition.

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 one-parameter read-only search with full schema coverage, no output schema needed, and annotations carrying the safety profile, the description is nearly sufficient: it defines what is matched and what is returned in kind. What remains missing is result shape/ordering and the meaning of the trailing review count, minor but not zero.

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?

Schema coverage is 100%, so the single parameter's type and length bounds are already documented. The description nevertheless adds non-trivial semantics: matching is a 'contains' operation against the page name only, not against theme or description text, which the schema does not state. That extra meaning justifies a 4 over the baseline 3.

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 gives a specific verb and resource: it returns site pages whose name contains the given text, and it enumerates the three page families covered (game, studio, collection pages). It goes further by stating the matching scope ('Nu ține cont de tema, subiect sau descriere'), so an agent can tell exactly what this lookup does. It stops short of naming the siblings (jackpoturi, rotiri_bune) for differentiation, which keeps it at 4.

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 an implied usage constraint in 'Nu ține cont de tema, subiect sau descriere' — use this when you know a page/entity name, not when you want topical or descriptive search. However, no explicit when-to-use or when-not-to-use statement is given, and no alternative tool is referenced, so the guidance must be inferred.

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