Skip to main content
Glama

submit_participant_vote

Submit availability votes (with optional "If Need Be" backup slots and email receipt) for a participant on candidate meeting slots or grid blocks

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": {
      "poll_id": "<poll_id>",
      "name": "<name>",
      "available_slot_indices": "<available_slot_indices>"
    },
    "name": "submit_participant_vote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesParticipant display name
emailNoParticipant email address
poll_idYesPoll ID or vanity slug
maybe_slot_indicesNoOptional array of 0-indexed "If Need Be" backup slot indices
send_voter_receiptNoWhen true and email is supplied, sends the voter an email copy of their selected availability and poll link
available_slot_indicesYesArray of 0-indexed candidate slot or grid block indices participant can attend

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / available_slot_indices / description
      Previous value: -"Array of 0-indexed candidate slot indices participant can attend"New value: +"Array of 0-indexed candidate slot or grid block indices participant can attend"
    • addedInput schema / properties / maybe_slot_indices
      Added value: +{
      +  "description": "Optional array of 0-indexed \"If Need Be\" backup slot indices",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / send_voter_receipt
      Added value: +{
      +  "default": false,
      +  "description": "When true and email is supplied, sends the voter an email copy of their selected availability and poll link",
      +  "type": "boolean"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / available_slot_indices / description
      Previous value: -"Array of 0-indexed candidate slot indices participant can attend [Required: non-empty valid value must be supplied]."New value: +"Array of 0-indexed candidate slot indices participant can attend"
    • changedInput schema / properties / email / description
      Previous value: -"Participant email address [Optional: omit to use server default filter]."New value: +"Participant email address"
    • changedInput schema / properties / name / description
      Previous value: -"Participant display name [Required: non-empty valid value must be supplied]."New value: +"Participant display name"
    • changedInput schema / properties / poll_id / description
      Previous value: -"Poll ID or vanity slug [Required: non-empty valid value must be supplied]."New value: +"Poll ID or vanity slug"
  3. Changed4 schema fields changed
    • changedInput schema / properties / available_slot_indices / description
      Previous value: -"Array of 0-indexed candidate slot indices participant can attend"New value: +"Array of 0-indexed candidate slot indices participant can attend [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / email / description
      Previous value: -"Participant email address"New value: +"Participant email address [Optional: omit to use server default filter]."
    • changedInput schema / properties / name / description
      Previous value: -"Participant display name"New value: +"Participant display name [Required: non-empty valid value must be supplied]."
    • changedInput schema / properties / poll_id / description
      Previous value: -"Poll ID or vanity slug"New value: +"Poll ID or vanity slug [Required: non-empty valid value must be supplied]."
  4. First observed

TDQS

C2.9/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 behavioral burden for a mutation tool. It mentions optional backup slots and that the email receipt requires an email, but says nothing about whether resubmission overwrites prior votes, whether the poll must be open, permission/identity requirements, rate limits, or what is returned on success or failure.

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?

A single front-loaded sentence that names the action, the actor, the target, and the optional extras with no filler. The nested parenthetical is slightly dense but still readable and earns its space by flagging the two optional behaviors.

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?

For a six-parameter write tool with no annotations and no output schema, the description is thin. It omits mutation semantics (overwrite vs append), precondition state of the poll, and any indication of the result, leaving the agent with meaningful uncertainty about consequences of calling it.

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%, so all six parameters are already documented, including the 'If Need Be' semantics for maybe_slot_indices and the email-dependency for send_voter_receipt. The description restates rather than extends that meaning, 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?

States a specific verb+resource: submits availability votes for a participant against candidate meeting slots or grid blocks. The parenthetical clarifies the two optional capabilities (backup slots, email receipt). It does not explicitly differentiate itself from siblings like check_poll_status or get_poll_consensus, but the write action is clearly distinct from those read-style names.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g., poll must be open, participant must exist), and no reference to alternatives. An agent must infer that this is the voting step of the poll workflow purely from the name and description.

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