trust-tools

explain_rating

Explain what an Obelisk Rating number means: its trust band, how the public scan scores, and what typically moves a score. Deterministic by default; pass narrate:true for an additional one-line model-written narrative (cached, public-scope, never required). Pure function of the number — no data is read.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`rating`	Yes	A 0-100 Obelisk Rating, e.g. from scan_trust or get_org_rating.
`narrate`	No	S283 — also return `narrative`, a one-sentence model-written reading of the band (deterministic fields are always present).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / narrate

Added value: +{
+  "description": "S283 — also return `narrative`, a one-sentence model-written reading of the band (deterministic fields are always present).",
+  "type": "boolean"
+}

First observedAug 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries full behavioral burden and does so excellently: it discloses determinism, the optional model-written narrative, caching, public scope, that the narrative is never required, and that the function reads no data. This gives an agent a clear safety and side-effect profile.

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 tightly packed sentences with no filler. The core purpose is front-loaded, followed by the optional behavior and a side-effect guarantee. Every clause earns its place.

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 pure function with two parameters and no output schema, the description is complete: it explains what will be returned conceptually, when narrate is needed, and that no data is read. Nothing an agent needs 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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains that narrate:true yields a one-line model-written narrative that is cached, public-scope, and never required, and that the rating is treated as a pure function. This helps the agent understand the optional parameter's behavior without opening the schema.

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?

States a specific verb and resource: explain what an Obelisk Rating number means, including trust band, scan score contribution, and movement drivers. This clearly distinguishes it from sibling tools that produce ratings (scan_trust, get_org_rating) rather than interpret them.

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 makes the call context clear: use this when you have an Obelisk Rating number and need its meaning, and it clarifies that narrate is optional. It does not explicitly name sibling alternatives or exclusion conditions, but the purpose is unambiguous enough that an agent can route correctly.

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

All trust-tools tools Inspect

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

Need Help?