Skip to main content
Glama
@three-ws/ibm-x402-mcp

@three-ws/ibm-x402-mcp

by nirholas

IBM Granite Analyze ($0.04)

ibm_granite_analyze
Read-only

Analyzes documents and returns structured JSON extracting entities, sentiment, risk signals, summaries, and next steps for contract, financial, or technical review.

Instructions

Structured document analysis powered by IBM Granite: extract entities, sentiment, risk signals, a concise summary, and recommended next steps from any text (contracts, reports, emails, code reviews, etc.). Returns a machine-readable JSON analysis. Use this when you need machine-readable fields (entities, sentiment, risks) from a document rather than the free-text reply ibm_granite_chat gives. No IBM Cloud account required — pay $0.04 USDC per call via x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "document": "<document>"
    },
    "name": "ibm_granite_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentYesThe document, report, email, or text to analyze.
languageNoDocument language hint (e.g. "Spanish", "French"). Defaults to auto-detect.
analysis_typeNoAnalysis focus: general (universal), contract (legal terms, obligations), financial (metrics, risks, forecasts), technical (architecture, issues), medical (clinical entities, findings), or sentiment (tone, emotions).general

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.4
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds genuinely new behavioral context: no IBM Cloud account required and a $0.04 USDC charge per call via x402, which is a cost/auth fact an agent planner must know. It stops short of describing non-determinism implied by idempotentHint=false or any latency/rate-limit traits.

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?

Four short sentences, front-loaded with the capability, then the decision rule, then cost/auth. Slight redundancy between "Returns a machine-readable JSON analysis" and the later phrase "machine-readable fields" in the usage sentence, but no padding otherwise.

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?

For a three-parameter analysis tool with no output schema, the description covers capability, return nature, sibling routing, and billing/auth prerequisites. The one real gap is return structure: it lists the analysis fields but not their shape, and there is no output schema to fall back on.

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%, and the enum values for analysis_type are already fully explained in the schema, so the baseline is 3. The description adds no extra guidance on parameter usage (e.g., when a language hint is worth supplying, or the 24,000-character cap), so it does not exceed the schema's contribution.

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?

Specifies a concrete verb and resource ("Structured document analysis") and enumerates the outputs the agent gets back (entities, sentiment, risk signals, summary, next steps). It also explicitly names the sibling it differs from (ibm_granite_chat) and the axis of difference (machine-readable fields vs. free-text reply).

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?

"Use this when you need machine-readable fields (entities, sentiment, risks) from a document rather than the free-text reply ibm_granite_chat gives" is an explicit when-to-use plus an explicit alternative, so the routing decision needs no inference. The document-domain examples (contracts, reports, emails, code reviews) further bound when it applies.

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