Skip to main content
Glama

Tru8 Evidence Research

by io.github.SamYatesSmith

tru8_get_result_raw

Read-onlyIdempotent

Retrieve a previously submitted check without computed analytics.

Returns claims, elements, evidence, and claim maps only. No _computed
block. Smaller response payload. Use this when you will compute your
own aggregations or only need specific fields from the raw data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
check_idYesThe check UUID returned by tru8_check. Same retrieval as tru8_get_result, without the computed analytics block.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description discloses valuable behavioral details: exactly which parts are returned (claims, elements, evidence, claim maps), what is excluded (no _computed block), and the consequence (smaller response payload). This gives the agent a clear expectation of the response content.

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?

The description is three sentences, each earning its place: the first states the core purpose, the second details return contents, and the third gives usage guidance. It is front-loaded with the key action and free of redundant text.

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 simple one-parameter read-only tool, the description is comprehensive: it explains the action, return contents, and when to use it. The output schema is present, annotations cover safety, and the sibling names provide retrieval context. Nothing important 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?

The input schema has 100% coverage; the check_id parameter already has a clear description referencing tru8_check and tru8_get_result. The tool description adds no parameter-specific meaning beyond what the schema provides, so the baseline of 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?

The description starts with a specific verb+resource+scope: 'Retrieve a previously submitted check without computed analytics.' It clearly differentiates from the sibling tool tru8_get_result by explicitly stating the absence of the _computed block and smaller payload.

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?

The description provides explicit when-to-use guidance: 'Use this when you will compute your own aggregations or only need specific fields from the raw data.' It does not explicitly name the alternative tool or state when not to use it, but the context and schema reference to tru8_get_result make the alternative clear.

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

All Tru8 Evidence Research toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

tru8_check is clearly the submission/analysis entry point, while tru8_get_result and tru8_get_result_raw both retrieve a previous check but are explicitly differentiated by whether computed analytics are included. The overlap is intentional and the descriptions make the choice clear.

Naming Consistency5/5

All tools share the tru8_ prefix and follow a consistent snake_case verb_noun pattern: check, get_result, get_result_raw. The raw suffix cleanly signals the variant without breaking the naming convention.

Tool Count5/5

Three tools is well-scoped for this service: one to submit an evidence check and two retrieval variants for different use cases. Each tool earns its place and there is no unnecessary bloat.

Completeness4/5

The core lifecycle of submitting a check and retrieving results is covered, including a raw option for custom processing. Minor gaps exist around discovering past checks or explicitly polling in-progress work, but the primary workflow has no dead ends.

Resources