Skip to main content
Glama

trouver_machines_a_sous

Read-only

Cette fonction localise les pages dont le nom comporte le texte donné : jeux, studios de jeux et collections. Les recherches par sujet, thème ou description ne sont pas couvertes. Jeux testés: 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": "trouver_machines_a_sous"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesDésignation entière ou partielle d’un jeu, d’un studio ou d’une collection, deux caractères au moins.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without description help. The description adds useful behavioral context by clarifying that only name fields are matched, not topics or descriptions. It says nothing about result volume, ordering or pagination, and the 'Jeux testés: 9' fragment is unexplained.

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?

Three short sentences, with the operation front-loaded before the scope exclusion. The final sentence 'Jeux testés: 9' is an unattributed fragment whose meaning is unclear, which slightly dilutes an otherwise tight description.

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 one-parameter, read-only lookup with no output schema, the description covers the matching semantics and exclusions adequately. It does not indicate what a result looks like (a list of pages?) or whether matching is case/accent sensitive, leaving minor gaps for a search tool.

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?

The single parameter has 100% schema description coverage, so the schema already states it is a full or partial designation of a game, studio or collection, minimum two characters. The description's 'texte donné' reinforces name-match semantics but adds no format or syntax detail beyond the schema, so 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 names a specific action ('localise les pages dont le nom comporte le texte donné') and enumerates the resource types searched: jeux, studios de jeux, collections. It also states the scope boundary (name matching only), so an agent knows what the tool does. It does not name any sibling tool, and the trailing fragment 'Jeux testés: 9' is cryptic and adds no clarity to the purpose.

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 explicitly excludes alternative interpretations with 'Les recherches par sujet, thème ou description ne sont pas couvertes', which tells the agent when NOT to use it. It does not point to a named alternative tool for those excluded cases, so the when-to-use routing is clear but incomplete.

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