Raze

get_available_slots

Check available Cal.com time slots for the Raze introduction event. This is read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`end`	Yes	End of the search range as an ISO 8601 date or date-time. Must be after start and within 31 days.
`start`	Yes	Start of the search range as an ISO 8601 date or date-time.
`format`	No	Cal.com slot response format. Defaults to range.
`duration`	No	Optional event duration in minutes.
`timeZone`	No	IANA time zone for returned slots, for example America/New_York. Defaults to UTC.

TDQS

B3.2/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 carry the full burden of behavioral disclosure. It mentions 'read-only' but fails to address other important behaviors such as authentication requirements, rate limits, or what happens if no slots are found.

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?

The description is extremely concise, consisting of two short sentences. The first sentence clearly states the purpose, and the second adds a behavioral note. No unnecessary words.

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?

The tool has 5 parameters and no output schema, but the description does not explain what the tool returns or how to interpret the results. This leaves agents without enough information to use the tool effectively.

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 input schema has 100% description coverage, so the description adds no additional meaning. It simply restates the tool's purpose without clarifying how parameters interact or providing context beyond the schema.

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 the action ('Check'), the resource ('available Cal.com time slots'), and the specific context ('Raze introduction event'). It effectively distinguishes itself from sibling tools (e.g., create_booking, get_pricing) by focusing on slot checking.

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?

The description lacks explicit guidance on when to use this tool versus its siblings. It only notes that the tool is 'read-only', but does not mention that it should be used before creating a booking, nor does it exclude inappropriate use cases.

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

All Raze tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation5/5

Each tool targets a distinct aspect of Raze's public information or booking functionality. There is no overlap; booking, pricing, projects, resources, and services are clearly separated.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_available_slots, list_projects). This makes it easy for an agent to predict tool behavior.

Tool Count5/5

With 10 tools, the server covers the main public-facing aspects of Raze (booking, pricing, projects, resources, services) without being overly heavy or thin. Each tool serves a clear purpose.

Completeness5/5

The tool set provides comprehensive coverage for a company site: booking lifecycle (including slot checking and creation), pricing, project case studies (list and detail), resources, and services. No obvious gaps for the intended public interaction.

Resources

Need Help?