HireSquire Agent Ecosystem

create_calendar_connection

Securely connect a scheduling provider to HireSquire using an API key. Use this during initial user onboarding or when adding a new interview tool.

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>",
      "api_key": "<api_key>"
    },
    "name": "create_calendar_connection"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	Yes	Valid API key/token from the provider.
`provider`	Yes	The scheduling tool provider.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedMay 16, 2026

changedInput schema / properties / api_key / description

Previous value: -"API key for the provider"New value: +"Valid API key/token from the provider."

removedInput schema / properties / calendar_id

Removed value: -{
-  "description": "Optional specific calendar ID",
-  "type": "string"
-}

changedInput schema / properties / provider / description

Previous value: -"Calendar provider"New value: +"The scheduling tool provider."

First observedMay 11, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It asserts the connection is 'secure' but does not say what happens when a key is invalid, whether credentials are validated or stored, whether an existing connection is overwritten, or whether the call is idempotent — all material for a credential-writing operation.

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 tight sentences with the action and the mechanism front-loaded, no filler. It could be marginally tighter but nothing is wasted.

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?

For a simple two-parameter credentialed write with a fully described schema and no output schema, the what and when are covered. However, with no annotations, the description should at least hint at validation, failure, and duplicate-connection behavior.

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% and the provider enum is documented, so the schema does the heavy lifting. The description only reinforces that api_key is a provider-issued token, adding no format, validation, or permission detail beyond the schema.

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 gives a specific verb and object ('connect a scheduling provider to HireSquire') plus the mechanism ('using an API key'), which is clearly distinct from the read-only sibling list_calendar_connections. It stops short of explicitly naming that sibling, so it falls just below a 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 states clear usage context: 'during initial user onboarding or when adding a new interview tool,' which tells the agent this is a setup-time creation action rather than a lookup. It offers no explicit exclusions or named alternative for cases like re-connecting or updating an existing provider.

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?