INITE

Free call times

inite_slots

Read-onlyIdempotent

The call times INITE's calendar has free, as ISO instants, with the call length and the host's time zone. Pass one of them to inite_book_call as starts_at.

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": "inite_slots"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Slots per page, default 10
`offset`	No	The nextOffset of the previous answer
`time_zone`	No	IANA zone to show the times in, e.g. America/Sao_Paulo

Output Schema

Name	Required	Description	Default
`limit`	No
`slots`	Yes
`total`	Yes
`offset`	No
`matched`	No
`nextOffset`	No
`durationMin`	No
`hostTimeZone`	No
`totalIsAtLeast`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedNov 3, 2026

changedInput schema / properties / limit / description

Previous value: -"How many free slots to return, soonest first (default 10)"New value: +"Slots per page, default 10"

addedInput schema / properties / offset

Added value: +{
+  "description": "The nextOffset of the previous answer",
+  "minimum": 0,
+  "type": "number"
+}

addedOutput schema / properties / limit
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / matched
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / nextOffset

Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / offset
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / total
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / totalIsAtLeast
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "slots"
-]New value: +[
+  "slots",
+  "total"
+]

First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and a closed-world scope, so the safety profile is covered. The description adds some context about returned value shape (ISO instants plus call length and host zone), but says nothing about pagination behavior, maximum window, or the possibility of an empty result set — and with an output schema present, return-format detail carries less weight.

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 sentences, with the resource scope front-loaded and the actionable instruction second — nothing is padded. The first sentence is syntactically awkward, which costs a point but not usability.

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 simple three-param read tool with full annotation coverage and an output schema, the description covers what the tool returns and the immediate next step. The remaining gap is pagination mechanics (offset/nextOffset flow), which the schema hints at but the description never confirms.

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 coverage is 100%, so limit, offset, and time_zone are already documented, and the description adds no parameter detail — baseline 3 applies. The one friction point is that the description says results come with "the host's time zone" while a time_zone parameter lets the caller pick the display zone, leaving the relationship between the two unstated.

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 the specific resource (free call times on INITE's calendar) and the output form (ISO instants, with call length and host time zone), which is enough to distinguish it from inite_book_call. The phrasing of the opening clause ("The call times INITE's calendar has free") is garbled and never uses an explicit verb like "list", so it falls short of a clean 5.

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 gives an explicit downstream handoff: "Pass one of them to inite_book_call as starts_at," which tells the agent exactly how this tool fits into a booking flow. It does not state any when-not conditions, prerequisites, or filtering behavior, so it stops short of full routing guidance.

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

All INITE tools Inspect

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.