Skip to main content
Glama
Sign In

toolzy

by io.toolzy
OverviewDiscussionsAdmin

Vérifier la disponibilité

check_availability

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 ?'.

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": {
      "tool_url": "<tool_url>",
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "check_availability"
  }
}

Input 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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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.

All toolzy toolsInspect
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