Skip to main content
Glama
Sign In

ScoreStory

by eu.scorestory
OverviewDiscussionsAdmin

Create personal invitation

invite_participant

Create a personal invitation for one participant and return their private link, for you or the person to pass on. scorestory does not e-mail the link from here; the person can do that from the survey's Invite page.

Input Schema

NameRequiredDescriptionDefault
nameNoThe participant's name. Give an email, a name, or both.
emailNoThe participant's email address. Give an email, a name, or both.
survey_idYesID of the survey, as returned by list_surveys or create_survey.
propertiesNoParticipant property values by property key, e.g. {"team": "Support"}. The keys are the survey's properties from get_survey; results can then be broken down by them.
external_idNoYour own identifier for the participant, e.g. an employee or customer number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / email / description
      Added value: +"The participant's email address. Give an email, a name, or both."
    • addedInput schema / properties / external_id / description
      Added value: +"Your own identifier for the participant, e.g. an employee or customer number."
    • addedInput schema / properties / name / description
      Added value: +"The participant's name. Give an email, a name, or both."
    • addedInput schema / properties / properties / description
      Added value: +"Participant property values by property key, e.g. {\"team\": \"Support\"}. The keys are the survey's properties from get_survey; results can then be broken down by them."
    • addedInput schema / properties / survey_id / description
      Added value: +"ID of the survey, as returned by list_surveys or create_survey."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare this is not read-only and not idempotent. The description adds important behavioral detail: no email is sent from this tool, and the return value is a private link. This goes beyond what annotations provide by clarifying the side effect and distribution expectation.

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, front-loaded with the core action and immediately followed by the key operational caveat (no email sent). No filler or redundancy.

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?

Given no output schema, the description adequately explains what is returned (a private link) and the key behavioral constraint (no email sent). Annotations cover idempotency and mutation semantics. Minor gap: it doesn't discuss rate limits or repeated invocation effects, but that is secondary for a simple creation tool.

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 five parameters (name, email, survey_id, properties, external_id) are fully documented in the schema. The description does not add any parameter-specific guidance beyond what the schema already states, so the baseline score of 3 is appropriate.

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 says exactly what the tool does: 'Create a personal invitation for one participant and return their private link.' It specifies the resource (personal invitation), scope (one participant), and output (private link). This clearly distinguishes it from sibling create_shared_link, which would not be personal or per-participant.

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?

The description explains how the link is meant to be used ('for you or the person to pass on') and explicitly notes that scorestory does not email the link, so the caller must distribute it via the survey's Invite page. It does not explicitly compare to alternatives like create_shared_link, but the context for when to use this tool is clear.

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

All ScoreStory toolsInspect
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