Skip to main content
Glama

Florian Preisenhammer · AI Transformation Lead

Get assessment questions

get_assessment_questions
Read-onlyIdempotent

Return the 25-question Empowered Team Health assessment (SVPG-based, 7 dimensions) to run with the user inside the chat. Each question has options A–D; pass the chosen option per question id to score_assessment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_assessment_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
dimensionNoOptional: filter by dimension.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds behavior beyond that: the exact size (25 questions), the option format (A–D), the question-id keying, and the intended conversational flow into scoring. It omits nothing critical for a fixed-size read, though it doesn't describe the shape of each returned question object.

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 tight sentences: the first front-loads what is returned and its scope, the second explains the follow-on action. Every clause carries information; nothing is filler.

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?

For a zero-required-parameter read tool with no output schema, the description supplies the essentials: result size, content structure, and next step. Only the per-question field layout and the effect of the dimension filter remain unstated, which are minor gaps here.

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 single enum parameter is fully documented in the schema, so the baseline is 3. The description mentions '7 dimensions' but never explains what passing a dimension filter actually does to the returned set (e.g., subset of questions), so it adds no real meaning beyond the schema.

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?

States a specific verb and resource ('Return the 25-question Empowered Team Health assessment') with concrete scope: fixed count, SVPG basis, 7 dimensions, A–D options. This clearly distinguishes it from siblings like get_ai_engineering_practice and list_assessments, which an agent can rule out without opening a schema.

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?

Gives clear usage context ('to run with the user inside the chat') and an explicit handoff rule: pass the chosen option per question id to score_assessment. It does not state when not to use it or address the optional dimension filter as an alternative mode, but the workflow routing is unusually clear.

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