Skip to main content
Glama

GMCA Certainty Matrix Validate

Haal de GMCA Certainty Matrix Validate-vragen op

get_validate_questions
Read-onlyIdempotent

Geeft de 11 officiële Validate-vragen terug, elk met een neutrale toelichting en voorbeeld. BELANGRIJK: stel elke vraag individueel en letterlijk aan de eindgebruiker en verzamel per vraag een antwoord Ja/Deels/Nee. Vul de vragen NOOIT zelf in op basis van een projectbeschrijving. De toelichting/voorbeeld mag je meegeven als de gebruiker twijfelt, maar mag het antwoord nooit sturen.

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_validate_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 safety (readOnly, idempotent, non-destructive, closed-world); the description adds the substantive behavioral constraint that answers must not be inferred or steered, and allows the explanation/example only as clarification. It describes the return payload loosely (11 items, each with toelichting and voorbeeld) but not its exact structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what is returned, then the critical usage constraint in caps, then the nuance about the explanation. Slight redundancy between the 'NOOIT zelf invullen' and 'mag het antwoord nooit sturen' sentences, but each adds a distinct rule.

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?

With no output schema and no parameters, the description carries the return-value burden and does describe the payload adequately (11 questions plus neutral explanation and example). It could be slightly more precise about how the questions are delivered (e.g. one call returning all 11), but an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies a parameterless retrieval.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific noun result: "Geeft de 11 officiële Validate-vragen terug, elk met een neutrale toelichting en voorbeeld" — an agent knows exactly what comes back. It does not name or contrast with its siblings (explain_validate_question, submit_validate_answers), so differentiation is only implicit through content.

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 unusually explicit operational rules: ask each question individually and literally, collect one answer per question on a Yes/Partly/No scale, and never self-answer from a project description. It stops short of routing to alternatives (e.g. what to do with answers afterwards), so it is strong context without explicit sibling hand-off.

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