Skip to main content
Glama

Outil.io

Search domains

search_domains
Read-only

Chercher un nom de domaine à acheter avec Outil : disponibilité et prix annuel TTC par extension proposée. q = nom seul (maboutique → .fr, .com…) ou domaine exact (maboutique.fr). Domaines premium non proposés.

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": {
      "q": "<q>"
    },
    "name": "search_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds what the call actually returns (availability plus annual price incl. tax per proposed extension) and the premium-domain exclusion, but says nothing about result volume, ranking, or lookup latency.

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

Conciseness5/5

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

Three short sentences: purpose and return data first, the q format second, scope exclusion last. Nothing is padded and the most decision-relevant information is front-loaded.

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 single-parameter, read-only lookup with annotations and no output schema, the definition covers what the tool does, what q accepts, and what is out of scope. Currency/region assumptions for 'prix annuel TTC' are the main unstated detail.

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 0%, so the description must carry the parameter, and it does: q accepts either a bare name ('maboutique' expanding to .fr, .com…) or an exact domain ('maboutique.fr'), with concrete examples. It doesn't mention the 191-char limit or behavior on malformed input, but the input format is otherwise clear.

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 specific verb and resource ('Chercher un nom de domaine à acheter') and states the returned data (availability, annual price incl. tax per extension). This makes it unmistakable among sibling search_* tools, though it never explicitly distinguishes itself from a named alternative.

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?

Usage is only implied by the resource itself (finding a buyable domain). The description does add a scope exclusion ('Domaines premium non proposés'), which is real guidance, but there is no statement of when to prefer this over another tool or of prerequisites.

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.