Skip to main content
Glama
Sign In

Nopaque TotalPath

by uk.co.nopaque
OverviewDiscussionsAdmin

Get Digital Test Config

getDigitalTestConfig
Read-onlyIdempotent

Get one saved digital (chat) test config by id: its name, kind, sector, mission, acceptance, pass and fail conditions, the bot it talks to (targetRef, connectorId or an inline target), its steps or probes, sample count and turn and time limits. Use when: you have a config id (from listDigitalTestConfigs) and want to explain what the test checks or which bot it reaches. Read-only. Needs digital:read. Returns 404 if the config is not in your workspace.

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": "getDigitalTestConfig"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description sensibly focuses on extra facts: the digital:read permission requirement and a 404 when the config is outside the caller's workspace. 'Read-only' partially restates readOnlyHint, which keeps it off a 5, but the auth and error behavior are genuine additions.

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?

One dense, front-loaded block: action and scope first, then the field enumeration, then usage, permissions, and error behavior. The long field list ('name, kind, sector, mission, acceptance, pass and fail conditions...') is informative but slightly catalogue-like; nothing is truly wasted.

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?

A single-parameter read tool with an output schema and full annotation coverage needs only trigger, permission, and failure-mode detail, and all three are present. Nothing an agent requires to invoke it correctly is missing.

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?

Schema coverage is 0% (the single `id` parameter has no description), so the description must compensate, and it does by naming `id` explicitly and stating where to obtain it (listDigitalTestConfigs). It does not restate the uuid format in the schema, so it adds real routing value rather than repeating structure.

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?

Opens with a specific verb and scoped resource ('Get one saved digital (chat) test config by `id`') and then enumerates the payload fields, which clearly separates it from getTestConfig and getMissionTestConfig by the 'digital (chat)' qualifier. An agent knows exactly what it will retrieve 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 Guidelines4/5

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

'Use when: you have a config id (from listDigitalTestConfigs) and want to explain what the test checks or which bot it reaches' gives an explicit trigger plus the upstream tool that produces the id. No when-not guidance or comparison against sibling getters, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Nopaque TotalPath toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources