Skip to main content
Glama

GMCA Certainty Matrix Validate

Licht een Validate-vraag toe met een voorbeeld

explain_validate_question
Read-onlyIdempotent

Geeft een korte, neutrale toelichting en een concreet voorbeeld bij één specifieke Validate-vraag. Roep dit ENKEL aan wanneer de gebruiker zelf aangeeft de vraag niet te begrijpen of twijfelt over de betekenis — nooit standaard, en nooit om zelf een antwoord te suggereren of in te vullen.

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": {
      "questionId": "<questionId>"
    },
    "name": "explain_validate_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionIdYesHet question-id uit get_validate_questions, bv. 'psf-1a'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the response is short and neutral, includes a concrete example, and must not hint at the answer. It does not describe length limits or formatting, but the essential behavioral contract is present.

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 action, followed by the usage constraint. Every clause carries information; nothing is redundant or padded.

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?

For a one-parameter, read-only tool with no output schema, the description covers what it does, what the response contains, and exactly when to invoke it. Nothing an agent needs in order to call it correctly is missing.

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 questionId parameter is documented in the schema with a concrete example ('psf-1a'). The description adds no further parameter meaning, so the baseline 3 applies.

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: it gives a short, neutral explanation plus a concrete example for one specific Validate question. The scope ('één specifieke Validate-vraag') distinguishes it from get_validate_questions (listing) and submit_validate_answers (submitting) without needing to open either schema.

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

Usage Guidelines5/5

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

Explicitly names the trigger condition (the user says they don't understand the question or doubts its meaning) and two exclusions: never by default, and never to suggest or fill in an answer. This is a full when/when-not specification with the key misuse case called out.

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