Skip to main content
Glama

search_tools

Chercher dans le catalogue Vantro les outils et services achetables (voyage, restauration, données, finance…). Renvoie prix, fiabilité mesurée et paramètres.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
categoryNo
max_price_eurNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It does disclose what comes back (prix, fiabilité mesurée, paramètres), which is useful, but says nothing about result limits, pagination, matching semantics, auth needs, or whether it is a read-only operation.

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 front-loaded sentences with no filler; the purpose comes first and the return fields second. It is tight, though the brevity comes at the cost of the guidance and parameter detail the agent needs.

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

Completeness2/5

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

With no annotations, no output schema, and 3 undocumented parameters, the definition should do considerably more work. As written the agent knows what the tool searches but not how to construct a call or what constraints apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters (query, category, max_price_eur) have 0% schema description coverage, so the description must compensate and does not. It never explains how query matching works, whether category accepts free text or fixed values, or that max_price_eur is a filter ceiling.

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 verb ("Chercher") and resource ("le catalogue Vantro les outils et services achetables") and adds domain examples (voyage, restauration, données, finance). It does not differentiate itself from siblings such as find_and_buy, which also appears to search-and-purchase, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The word "achetables" hints that this is discovery rather than purchase, but the agent receives no signal about when to pick this over find_and_buy or get_tool.

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