Skip to main content
Glama

Amalgix

by io.github.Amalgix-io

Analyze Document

analyze_document
Read-onlyIdempotent

Analyze a document using Crucible™ Evidence Engine. Returns source-grounded findings with evidence, confidence, verification status, and routing metadata. Use specialized financial/contract tools when the domain is known.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAnalysis question or focus area
formatNoOptional: Force a specific input format. Default: auto-detect via magic bytes.
tickerNoOptional ticker/company symbol metadata for financial filing analysis.
contentNoDocument content to analyze (max 20MB). Required unless fileUrl is provided. Accepts: (1) plain text, (2) Base64-encoded file with data URI prefix (e.g., "data:application/pdf;base64,..."), or (3) raw Base64 binary for text-extractable source documents. PRIVACY NOTICE: Content is transmitted to third-party LLM providers for processing. Do NOT submit documents containing passwords, private keys, SSNs, or other regulated PII.
fileUrlNoOptional: HTTPS URL to download the document from. If provided, content field is ignored. Use text-extractable source documents. Max 20MB.
sourceTypeNoOptional source type metadata for Crucible™ routing and output metadata.
analysisTypeNoOptional Crucible™ analysis mode. Default: auto.
jurisdictionNoOptional contract jurisdiction metadata. Output remains evidence triage, not legal advice.
partyPerspectiveNoOptional contract review perspective. Default: neutral.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaYesProcessing metadata
analysisYes

TDQS

A4.4/5.0
Behavior4/5

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

With readOnlyHint, openWorldHint, idempotentHint, and destructiveHint already provided, the description adds value by describing the output nature ('source-grounded findings with evidence, confidence, verification status, and routing metadata') and hints at non-legal advisory status via parameter context. It does not contradict annotations and offers useful behavioral context beyond the safety flags.

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 concise sentences: purpose, output summary, and usage guidance. Every sentence earns its place with no fluff or redundancy. It is front-loaded with the primary action and then provides key differentiators.

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?

Given the tool's complexity (9 parameters, output schema present), the description provides adequate high-level context: what it does, what it returns, and when to avoid it. It does not explain return values because the output schema exists. Minor gaps (e.g., no mention of size limits) are covered by the schema, making this description sufficient for selection and invocation.

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 description coverage is 100%, so the baseline is 3. The main description does not add parameter-level semantics, leaving the schema to fully document parameters. This is appropriate; no additional detail is required from the description itself.

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 action ('Analyze a document') and its resource/engine (Crucible™ Evidence Engine). It also differentiates from siblings by explicitly directing users to specialized financial/contract tools when the domain is known, making its general-purpose scope evident.

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 when-not-to-use guidance ('Use specialized financial/contract tools when the domain is known'), implying this tool is for general document analysis when the domain is unknown. This directly addresses alternatives among sibling tools.

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

All Amalgix 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.2/5.0
Disambiguation4/5

Each tool targets a clearly distinct operation: general analysis, public filing analysis, contract risk, summarization, web extraction, translation, cost estimation, and health check. While analyze_document could overlap with specialized tools, the descriptions provide clear guidance to use the specialized tools for known domains.

Naming Consistency4/5

Most tools follow a verb_noun snake_case pattern (analyze_document, estimate_cost, extract_web, review_contract_risks). Minor deviations include the bare verb 'summarize' and the noun-like 'health_check', and 'delegate_bulk_translate' uses an unusual verb prefix.

Tool Count5/5

8 tools is well within the typical 3-15 range, and each tool serves a distinct function that justifies its inclusion, including supporting utilities for cost estimation and health checks.

Completeness4/5

The toolset covers general analysis, specialized financial/contract analysis, summarization, web extraction, and translation. It lacks some potential operations like batch analysis or language listing, but the core workflows are supported without obvious dead ends.

Resources