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

@three-ws/ibm-x402-mcp

by nirholas

IBM Granite Chat ($0.02)

ibm_granite_chat
Read-only

Send role/content messages to IBM Granite models and get assistant replies with token usage; supports open-ended chat and free-form text generation without an IBM Cloud account.

Instructions

Chat completion powered by IBM Granite foundation models (default: ibm/granite-3-8b-instruct). Send a conversation as role/content message pairs and receive the assistant reply with token usage. Use this for open-ended conversation or free-form text generation; for code tasks call ibm_granite_code, and for structured JSON extraction call ibm_granite_analyze. No IBM Cloud account required — pay $0.02 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": {
      "messages": "<messages>"
    },
    "name": "ibm_granite_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOverride the Granite model id (e.g. ibm/granite-3-2b-instruct). Defaults to ibm/granite-3-8b-instruct.
messagesYesConversation history. Must include at least one user message.
temperatureNoSampling temperature (0 = deterministic). Defaults to 0.7.
max_new_tokensNoMaximum tokens to generate. Defaults to 1024.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.4
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / messages / items / additionalProperties
      Removed value: -false
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare read-only, open-world, non-idempotent, and non-destructive behavior. The description adds useful context beyond annotations: no IBM Cloud account is required, each call costs $0.02 USDC via x402, and the response includes the assistant reply with token usage. It does not cover latency, rate limits, or failure modes, but the annotations carry much of the safety 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?

The description is three tight sentences, front-loaded with the purpose and followed by routing guidance and payment details. Every sentence adds useful information without repetition.

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 chat-completion tool with four documented parameters and annotations covering safety behavior, the description supplies the missing context an agent needs: what it returns, when to choose it over siblings, and the auth/payment model. No output schema exists, but the description still states that the assistant reply and token usage are returned.

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 all four parameters are already documented in the input schema. The description restates the role/content message-pair structure and the default model, both of which are also in the schema, and adds no new parameter-level semantics.

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 states a specific action and resource: chat completion powered by IBM Granite foundation models, with the default model named. It also distinguishes this tool from siblings by directing code tasks to ibm_granite_code and structured JSON extraction to ibm_granite_analyze.

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?

It explicitly says to use this for open-ended conversation or free-form text generation, and names the alternative tools for code and structured extraction. The when-to-use and when-to-use-something-else guidance is clear.

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