Skip to main content
Glama

get_trust_report

Read-onlyIdempotent

Assesses trustworthiness of an event extraction by providing confidence score, multi-source cross-validation, and extraction quality metrics. Use to verify event reliability before making trading decisions.

Instructions

Get a trust and verification report for a single event. Returns: confidence_tier + confidence_score (heuristic 0-1), multi-source cross-validation details (which sources agree/disagree), and extraction quality metrics from the review system (regex vs LLM conflict count, llm_validation status, whether human-reviewed). Use when: you need to assess how reliable or trustworthy an event's extraction is — e.g. before making a trading decision based on the event data. Do NOT use when: you only need the event data itself (use get_event_detail), or when browsing/searching (use search_events_by_* tools). Returns a trust report object: {event_id, confidence_tier, confidence_score, confidence_reasons, cross_validation: {sources_checked, sources_agree, sources_disagree, source_details}, extraction_quality: {total_fields_reviewed, regex_llm_conflicts, llm_validation, human_reviewed}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
event_idYesEvent UUID v4. Example: 'c8a7f9e1-d2b4-4a3c-8d5e-1f6a9b3c7d4e'
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it details the return object structure (confidence_tier, confidence_score, cross-validation details, extraction quality metrics). Annotations already indicate read-only, non-destructive behavior, and the description aligns, providing no contradictions.

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?

The description is well-structured with front-loaded purpose and usage guidelines, but the return object specification is somewhat verbose. Could be slightly more concise, but still effective.

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?

Given no output schema, the description fully specifies the return object. With only one parameter and clear usage context, the description is complete for the tool's complexity.

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% for the single parameter (event_id). The description does not add meaning beyond the schema's description, which is adequate. Baseline of 3 is appropriate.

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 clearly states the tool's purpose: 'Get a trust and verification report for a single event.' It uses a specific verb ('Get') and resource ('trust report') and explicitly distinguishes from sibling tools by naming alternatives (get_event_detail, search_events_by_*).

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?

The description provides explicit 'Use when' and 'Do NOT use when' guidance, citing specific alternatives (get_event_detail, search_events_by_* tools). This fully informs the agent about appropriate invocation context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NengjiangLunpi/astockevent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server