RooQuiz

get_examinee

Read-only

View the full detail of one examinee (a.k.a. respondent) in the current team by its examineeId (the business ID shown in list_examinees, e.g. AB1234567890), including customData. Sensitive auth fields are never returned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`examineeId`	Yes	The examinee business ID (e.g. AB1234567890), as shown in list_examinees

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Masked name (J*n)
`email`	No	Masked email (j***g@example.com); never pass it back as an argument
`avatar`	No	Uploaded avatar as { id, url }
`status`	No	Account status
`tenant`	No	Team (tenant) the respondent belongs to
`createdAt`	No	ISO datetime of first sign-up
`updatedAt`	No	ISO datetime of the last change
`customData`	No	Team-defined custom fields; phone-typed values come back masked
`examineeId`	No	Business ID of the respondent (e.g. AB1234567890) — use it to address them
`avatarPreset`	No	Preset avatar key, when no image was uploaded
`emailVerified`	No	Whether the email has been verified

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedAug 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnlyHint and destructiveHint, and the description adds useful behavioral details: scoping to the current team and explicitly stating that sensitive auth fields are never returned.

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?

The description is two concise, front-loaded sentences with no filler. It covers the key facts in order: action, scope, identifier, included data, and an important security guarantee.

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?

Given one well-documented parameter, read-only annotations, and an output schema being present, the description is complete enough for an agent to correctly select and call the tool. Team scope, ID source, included data, and excluded fields are all stated.

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 the schema already documents examineeId as the business ID shown in list_examinees. The description repeats the same example and adds little beyond what the parameter schema already provides.

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 ('View the full detail of one examinee') and a specific resource, clearly distinguishing a full single-record lookup from list_examinees. It also mentions the key identifier and that customData is included.

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 clearly sets the context: use this on an examinee in the current team, and find the examineeId from list_examinees. It does not explicitly name alternatives or exclusions, but the intended read-only retrieval flow is clear.

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

All RooQuiz tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, especially the form, question, and translation families. The main ambiguity is between the lead/record tools: list_leads/get_lead vs list_records/get_record both describe entities as 'leads' even though one is the CRM lead and the other is the submission record. update_form vs update_form_settings is also a minor naming overlap, but the descriptions resolve it.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_*, list_*, create_*, update_*, delete_*, add_*, set_*, etc. Even paired image upload tools follow the same convention with prepare_/finalize_. There is no camelCase or mixed verb-style chaos.

Tool Count2/5

48 tools is far above the 25-tool threshold for a heavy tool surface. While the server covers a broad platform (forms, translations, leads, bookings, examinees, tenants, images), the sheer number will burden an agent's tool-selection step. Each tool may earn its place, but the overall set is too large for easy navigation.

Completeness4/5

The toolset provides solid lifecycle coverage for forms, questions, translations, leads, bookings, examinees, and tenant administration. Minor gaps exist, such as no lead deletion/export and no way to create or delete examinees, but agents can work around these for the core quiz-and-CRM workflow. The form/translation/question CRUD surface is especially thorough.

Resources

Need Help?