HireSquire Agent Ecosystem

get_available_slots

Query a connected calendar for open interview windows on a specific date. Use this to present valid time options to a candidate before scheduling.

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": {
      "provider": "<provider>",
      "date": "<date>"
    },
    "name": "get_available_slots"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Target date in YYYY-MM-DD format.
`duration`	No	Interview length in minutes.
`provider`	Yes	The connected provider to query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedMay 16, 2026

changedInput schema / properties / date / description

Previous value: -"Date in Y-m-d format"New value: +"Target date in YYYY-MM-DD format."

addedInput schema / properties / duration / default
```
Added value: +60
```

changedInput schema / properties / duration / description

Previous value: -"Duration in minutes (default 60)"New value: +"Interview length in minutes."

changedInput schema / properties / provider / description

Previous value: -"Calendar provider (Calendly or Cal.com)"New value: +"The connected provider to query."

First observedMay 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations present, the description carries the full disclosure burden. Saying 'a connected calendar' usefully implies a prerequisite connection (relevant given create_calendar_connection exists) and 'query' implies read-only, but it says nothing about the timezone of returned windows, behavior when the provider isn't connected, or whether results are live or cached. Those are meaningful gaps for an availability tool, so it earns partial credit only.

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, no filler, with the core operation stated first and the usage cue second. Every clause carries information.

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 three-parameter read tool with a fully documented schema and no output schema, the definition covers purpose, scope, and intent adequately. The remaining gap is that an agent cannot infer the timezone convention of the returned windows from either the schema or description.

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%, covering date format, duration default, and the provider enum, so the schema already does the heavy lifting. The description adds no additional meaning about how duration affects slot generation or how provider selection constrains results, so the baseline 3 applies.

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 a specific verb and resource: 'Query a connected calendar for open interview windows on a specific date.' That is unambiguous and clearly separable from write-oriented siblings like create_interview or create_calendar_connection. It stops short of naming an alternative when another read tool might overlap, so it lands at 4 rather than 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?

'Use this to present valid time options to a candidate before scheduling' gives a concrete usage context and an implied ordering relative to create_interview. There are no explicit exclusions or named alternatives, which caps it at 4.

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

All HireSquire Agent Ecosystem 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.

Resources

Need Help?