Skip to main content
Glama

cautare_rotiri

Read-only

Funcție de căutare în numele paginilor: selectează paginile de jocuri, studiouri și colecții care conțin textul dat în denumire. Căutarea nu acoperă subiectul, tema sau descrierea. Numărul recenziilor de jocuri: 19

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_rotiri"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesTermenul de căutare desemnează un joc, un studio de jocuri sau o colecție prin nume ori printr-un fragment de cel puțin două caractere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by limiting the search to page names and excluding other fields. However, the trailing sentence 'Numărul recenziilor de jocuri: 19' is unexplained and does not contribute to behavioral understanding.

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 core search behavior and exclusions are front-loaded and easy to parse. However, the final sentence about the number of game reviews is irrelevant to the tool definition and introduces unnecessary noise.

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 simple read-only search tool with one fully described parameter and relevant annotations, the description covers scope and exclusions adequately. It does not describe return format or result ordering, but for a basic name search this is a minor omission.

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%, and the single parameter is already documented as a search term with a minimum length of two characters. The description reiterates that the term refers to a game, studio, or collection name or fragment, adding only marginal meaning beyond the schema.

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: it searches page names for game, studio, and collection pages containing the given text. It also clarifies that the search is name-only and excludes subject, theme, and description. It does not explicitly differentiate itself from sibling tools, which keeps it at a 4 rather than a 5.

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?

The description gives clear usage context by specifying what the search covers and explicitly excludes subject, theme, and description content. This helps an agent decide when this search is appropriate versus searching other fields. However, it does not name or route to an alternative tool for those excluded search scopes.

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