Skip to main content
Glama

Tru8 Evidence Research

by io.github.SamYatesSmith

tru8_get_result

Read-onlyIdempotent

Retrieve a previously submitted check with pre-computed analytics.

Returns the full result including a _computed block with tier/type
distributions, corroboration groups, diagnostic values, timeline
analysis, element state summaries, and per-claim dispositions.

Use this over tru8_get_result_raw when you want structured analytics
ready for summarisation or comparison without post-processing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
check_idYesThe check UUID returned by tru8_check. Retrieval is free and limited to your own checks; a check still running returns its status rather than a result, so this is also the poll call.

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the _computed block contents and the differentiation from the raw variant, but does not mention that a still-running check returns status rather than a result (that nuance lives in the parameter schema). This is acceptable but not deeply transparent on its own.

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?

Three sentences each earn their place: the first defines the action, the second enumerates return contents, the third gives usage guidance. No filler, front-loaded, and appropriately sized.

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 a rich schema description, annotations, and an output schema present, the overall tool definition is quite complete. The description covers purpose, return contents, and alternative usage; only the polling behavior is left to the schema, which is acceptable. Missing error conditions or permission details, but those are not required.

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 schema has 100% coverage and the check_id description already explains that it's the UUID from tru8_check, mentions retrieval limits, and notes it serves as the poll call. The tool description adds no extra parameter semantics, so 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?

The description opens with 'Retrieve a previously submitted check with pre-computed analytics', clearly stating the verb and resource. It distinguishes this tool from tru8_get_result_raw by noting it returns structured analytics, making it easy to select the right tool.

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 states 'Use this over tru8_get_result_raw when you want structured analytics ready for summarisation or comparison without post-processing', providing both a when-to-use condition and a named alternative.

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