Skip to main content
Glama

toolzy

by io.toolzy
OverviewDiscussionsAdmin

Server Details

Recherche et location d'outils entre particuliers en France via Toolzy.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 38 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: searching for tools, retrieving detailed information, and checking availability/pricing. No overlap exists between these operations.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: check_availability, get_tool_details, search_tools. This makes the API predictable and easy to navigate.

Tool Count5/5

With only 3 tools, the server is tightly scoped to the core task of discovering and checking tool rental options. Each tool is essential and earns its place, fitting within the ideal 3-15 range.

Completeness3/5

The server covers the discovery and availability-checking workflow well, but lacks a booking or reservation tool, which is a notable gap for a rental platform. Users can find, inspect, and check a tool's availability, but cannot complete the rental, creating a dead end.

Available Tools

3 tools
check_availabilityVérifier la disponibilitéAInspect

Vérifie si un outil est disponible pour des dates données et calcule le prix total. Utilisez ce tool quand l'utilisateur demande la disponibilité, veut savoir le prix pour une période, ou demande 'est-ce disponible ce weekend ?'.

ParametersJSON Schema
NameRequiredDescriptionDefault
end_dateYesDate de fin (YYYY-MM-DD)
tool_urlYesURL de l'annonce Toolzy (ex: https://www.toolzy.io/listings/perceuse-makita)
start_dateYesDate de début (YYYY-MM-DD)

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It only states the tool checks availability and calculates price, but omits any side effects, permissions, or what 'available' means (e.g., return format). Lacks depth.

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?

Two sentences, each serving a distinct purpose: stating function and providing usage examples. No redundancy or filler.

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?

With no output schema, the description should hint at return values. It does not. Three parameters are simple and all required, but the description is adequate for a basic tool, leaving some gaps.

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 covers all three parameters with descriptions. The description does not add extra meaning 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it checks availability for given dates and calculates total price. It distinguishes from sibling tools (get_tool_details, search_tools) which serve different purposes.

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?

Provides explicit use cases (availability queries, price inquiries, 'is it available this weekend?'). Does not mention when NOT to use, but the examples are clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_tool_detailsDétails d'un outilAInspect

Récupère les informations détaillées d'un outil sur Toolzy : prix, caractéristiques, photos. Utilisez ce tool quand l'utilisateur veut en savoir plus sur un outil spécifique après avoir vu les résultats de recherche. Renvoie aussi similar_tools : des alternatives de la même catégorie dans un rayon de 20 km avec leur distance — à proposer si l'outil est jugé trop cher ou trop loin.

ParametersJSON Schema
NameRequiredDescriptionDefault
tool_urlYesURL de l'annonce Toolzy (ex: https://www.toolzy.io/listings/perceuse-makita)

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses what is returned (price, features, photos) and the similar_tools behavior, including distance within 20 km and a usage policy (suggest if too expensive or too far). It could cover error cases, but for a simple detail-lookup tool this is transparent.

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?

Two sentences, fully front-loaded with purpose and usage. Every clause adds value, including the similar_tools guidance. Zero redundancy and appropriately sized for the tool's complexity.

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?

The tool has one parameter, no output schema, and no annotations. The description adequately covers the return values and usage context. It is nearly complete, though it does not mention behavior when no similar tools exist or if the URL is invalid.

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%, with tool_url already documented including an example URL. The description does not add parameter-level semantics beyond the schema, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: 'Récupère les informations détaillées d'un outil sur Toolzy' with clear scope (prix, caractéristiques, photos). It distinguishes from siblings by implying search_tools is for finding tools and positioning this tool as the follow-up for a specific tool.

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 says when to use the tool: 'quand l'utilisateur veut en savoir plus sur un outil spécifique après avoir vu les résultats de recherche.' This gives clear context but does not explicitly name alternatives or exclusion scenarios, which keeps it a step below a perfect score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_toolsRechercher des outilsAInspect

Recherche d'outils et équipements disponibles à la location sur Toolzy. Utilisez ce tool quand l'utilisateur cherche un outil, veut louer du matériel, ou demande ce qui est disponible près de chez lui (ex: 'perceuse à Bordeaux', 'tondeuse à gazon', 'outils de bricolage'). La recherche couvre la commune demandée PUIS les communes voisines dans un rayon de 15 km : chaque résultat porte is_local et distance_km, et search_area donne la répartition. Indiquez toujours à l'utilisateur ce qui est dans sa ville et ce qui est à côté, avec la distance.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNoVille de recherche. Les communes voisines sont incluses automatiquement.
limitNoNombre max de résultats (défaut: 10, max: 20)
queryNoRecherche textuelle (nom d'outil, marque, type)
countryNoMarché à interroger, pour lever une ambiguïté de commune homonyme (ex: Bruges).
zipcodeNoCode postal (filtre par préfixe)
categoryNoCatégorie d'outils
coachingNoFiltrer sur accompagnement disponible
deliveryNoFiltrer sur livraison disponible
price_maxNoPrix maximum par jour en euros
radius_kmNoRayon autour de la ville en km (défaut: 15). N'élargissez que si l'utilisateur accepte de se déplacer plus loin.

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses important behavioral traits: search first covers the requested commune then neighboring communes within 15 km, each result includes `is_local` and `distance_km`, and `search_area` shows the breakdown. It also gives a user-communication mandate, adding value beyond the schema, though it does not detail sorting, pagination, or exact result shape.

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?

The description is four sentences and each one adds value: defining the search scope, giving user-intent triggers, explaining geographic behavior, and instructing the assistant on how to present results. It is slightly long but remains focused and front-loaded with the core purpose.

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?

Given 10 parameters and no output schema, the description provides crucial runtime behavior (radius expansion, result fields) and user-facing guidance. It does not fully specify the response structure beyond `is_local`, `distance_km`, and `search_area`, but it is sufficient for an agent to select and invoke the tool correctly in most cases.

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%, so the structured schema already documents all 10 parameters. The description adds little new parameter-level information; it restates the radius default and expansion behavior, but the schema already covers those details. The description does not meaningfully compensate beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: "Recherche d'outils et équipements disponibles à la location sur Toolzy," clearly stating the tool searches for rentable tools/equipment. It distinguishes itself from sibling tools (check_availability, get_tool_details) by being the search/query entry point with examples like "perceuse à Bordeaux".

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

Usage Guidelines5/5

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

Explicit usage guidance is provided: "Utilisez ce tool quand l'utilisateur cherche un outil, veut louer du matériel, ou demande ce qui est disponible près de chez lui" with concrete examples. It also explains the search radius behavior and instructs the agent to always tell the user what is local vs. nearby, which is actionable context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedsearch_tools3 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"Ville pour filtrer les résultats"New value: +"Ville de recherche. Les communes voisines sont incluses automatiquement."
      • addedInput schema / properties / country
        Added value: +{
+  "description": "Marché à interroger, pour lever une ambiguïté de commune homonyme (ex: Bruges).",
+  "enum": [
+    "france",
+    "belgique"
+  ],
+  "type": "string"
+}
      • addedInput schema / properties / radius_km
        Added value: +{
+  "description": "Rayon autour de la ville en km (défaut: 15). N'élargissez que si l'utilisateur accepte de se déplacer plus loin.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "number"
+}
  2. 3 tool updates
    • First observedcheck_availability
    • First observedget_tool_details
    • First observedsearch_tools

Related MCP Connectors

Related MCP Servers

  • Toolzy MCP Server by Toolzy-2

    Toolzy MCP Serverofficial

    Toolzy-2
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI assistants to search, view details, and check availability of tool rental listings from Toolzy's peer-to-peer marketplace.
    MIT

  • RenooLab MCP

    mehdimicra
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables users to find and contact building tradespeople in France, and lets independent tradespeople create free profiles.
    Apache 2.0

  • leboncoin-mcp

    arthur-c
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI assistants to search and consult Leboncoin classified ads through the MCP protocol, with tools for ad search, detail retrieval, user profiles, and category/region listings.
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources