Skip to main content
Glama

DECA Labs

Read a test

get_test
Read-only

A paid test's state and everything in it: payment, review, the pass line, progress and the result. Readable with the key it was paid with, or its access_token.

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": {
      "id": "<id>"
    },
    "name": "get_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe test's id.
access_tokenNoThe access_token start_test returned, when the test was paid without a key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: the access model (paid key or access_token), which is a real precondition an agent must satisfy before calling.

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?

Two sentences with no filler, and the payload contents are front-loaded ahead of the access condition. The colon-separated field list is dense but readable and each item is informative.

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 only two fully documented parameters and no output schema, the definition does its job by enumerating the returned sections (payment, review, pass line, progress, result). What is missing is minor: no note on error behavior when the credential is wrong or the test is unpaid.

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%, so both parameters are already documented, and the description largely restates the access_token semantics rather than extending them. The one added signal is that the two credentials are alternatives ('or'), which the schema does not state explicitly.

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?

The description names the resource ('a paid test') and enumerates exactly what the read returns: payment, review, the pass line, progress and the result. It is far more specific than a tautology like 'Get a test', but it never contrasts itself with list_my_tests or get_ideas, so sibling differentiation is left implicit.

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?

Usage is implied by 'Readable with the key it was paid with, or its access_token', which tells the agent which credential to supply, but there is no explicit when-to-use statement and no guidance on when to prefer this over list_my_tests or get_ideas.

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