Skip to main content
Glama

Florian Preisenhammer · AI Transformation Lead

Score an assessment

score_assessment
Read-onlyIdempotent

Score a completed Empowered Team Health assessment. Provide the chosen option (A/B/C/D) per question id. Returns the overall score, per-dimension scores with bands (low/mid/high) and coaching guidance.

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": {
      "answers": "<answers>"
    },
    "name": "score_assessment"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesOne answer per question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, closed-world), so the description's real contribution is disclosing the return shape — overall score plus per-dimension scores with low/mid/high bands and coaching guidance — which matters because no output schema exists. It stops short of saying whether submissions are persisted or how invalid/incomplete answer sets are handled, but it is consistent with the annotations and adds genuine behavioral context.

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?

Three short sentences: purpose first, required input second, return value third. Nothing is redundant with the title, and no sentence could be removed without losing information.

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 single-parameter, non-destructive tool with no output schema, the description supplies everything needed to call it and to know roughly what comes back. The remaining gaps — the question-id source and behavior on incomplete or invalid answers — are modest but real for a scoring operation that expects one answer per question across 25 questions.

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%, and the schema itself documents the nested id and option fields, so the baseline is 3. The description reinforces the enumeration (A/B/C/D) and the one-answer-per-question expectation but adds no format, ordering, or validation semantics beyond what the 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?

Names a specific verb and resource ("Score a completed Empowered Team Health assessment") and uses the second sentence to state the required input shape, which cleanly separates it from siblings such as list_assessments (which enumerates rather than scores) and get_assessment_questions (which supplies the ids). An agent can identify the operation without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies the usage condition (a completed assessment, with the chosen option per question id), which is enough to infer when the tool applies, but it never states prerequisites explicitly — notably that question ids must be obtained from get_assessment_questions first — nor what to do with partially completed assessments. No alternatives or exclusions are named.

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