Skip to main content
Glama

Send Clarity Interview Invites

sendClarityInterviewInvites

Invite people to record an interview about this Clarity process, and email each of them. To invite people from the organization chart or landscape, first use the Clarity hierarchy people tools to find their names and email addresses, then pass them as invitees. Set includeProcessPeople to true to also invite everyone already listed as a person on this process. At most 25 unique recipients per call. Each invitee gets a Clarity process invitation, exactly as the Invite dialog creates one; someone already invited is sent their invitation again rather than a second one. Where the team has account-free interview links on, people without a Duvo account get a link that opens the interview directly and expires after 30 days, or seven days after a scheduled interview ends if that is later; everyone else gets the normal invitation that asks them to sign in. Pass schedule to book the interview: the email then carries a calendar invite for that time, sending again with a new time moves the same calendar event, and revoking the invitation cancels it. Revoke a pending invitation with deleteTeamInvite.

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": {
      "id": "<id>"
    },
    "name": "sendClarityInterviewInvites"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe Clarity process ID.
messageNoOptional plain-text note added to each invitation email, at most 500 characters. Line breaks are collapsed and markup is shown as text.
inviteesNoPeople found through org-chart or landscape people tools. At most 25 unique recipients per call, counting includeProcessPeople.
scheduleNoOptional time for the interview. The invitation email then carries a calendar invite for it, the interview link stays valid until a week after it, and a later send with a new time moves the same calendar event. At most 90 days ahead. Only available while calendar invites are on for the team.
includeProcessPeopleNoAlso invite every active process person with an email address. Use this for people already assigned to the process.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / schedule
      Added value: +{
      +  "description": "Optional time for the interview. The invitation email then carries a calendar invite for it, the interview link stays valid until a week after it, and a later send with a new time moves the same calendar event. At most 90 days ahead. Only available while calendar invites are on for the team.",
      +  "properties": {
      +    "durationMinutes": {
      +      "description": "How long the interview is booked for, 15 to 240 minutes.",
      +      "maximum": 240,
      +      "minimum": 15,
      +      "type": "integer"
      +    },
      +    "startAt": {
      +      "description": "When the interview starts, as an ISO 8601 date-time with an offset or Z, e.g. 2026-10-28T10:00:00+01:00. Must be in the future and at most 90 days ahead.",
      +      "format": "date-time",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +      "type": "string"
      +    },
      +    "timeZone": {
      +      "description": "IANA time zone the time is shown in, e.g. Europe/Prague. The calendar shows it in each reader's own zone.",
      +      "maxLength": 64,
      +      "minLength": 1,
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "startAt",
      +    "durationMinutes",
      +    "timeZone"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses meaningful behavior: a 25-recipient cap, resend-instead-of-duplicate behavior for existing invitees, account-free link expiration rules, and calendar-event behavior when a new schedule is supplied. The description also explains that revocation cancels a booked calendar event, which is exactly the kind of side-effect context an agent needs for a non-read-only, open-world action.

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?

The purpose is front-loaded and most sentences carry operational value, but the description is dense and long, with several complex clauses packed into single sentences. It remains readable and largely waste-free, though stronger structure would improve scanability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex emailing and scheduling operation with no output schema, the description covers the important behavioral edges: invitee limits, existing-invite handling, account-free links, scheduling side effects, and revocation. Permission requirements are not stated, but the core information needed to invoke and reason about the tool is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 100%, the schema already documents all parameters. The description still adds useful meaning beyond the schema by explaining how invitees should be sourced, that includeProcessPeople counts toward the 25-recipient limit, and how schedule affects calendar invites and later resends.

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 states a specific verb and resource: invite people to record a Clarity process interview and email each of them. It also distinguishes the operation from related actions such as finding people via hierarchy tools and revoking with deleteTeamInvite, so an agent can identify the tool without confusion.

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 clear usage context: use hierarchy people tools first for org-chart or landscape invitees, set includeProcessPeople to invite existing process people, pass schedule to book a time, and use deleteTeamInvite to revoke. It does not explicitly compare against other invite-related siblings such as bulkCreateTeamInvites or listClarityInterviewInvites, leaving some sibling-selection guidance implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources