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

@three-ws/ibm-x402-mcp

by nirholas

IBM Granite Embed ($0.005)

ibm_granite_embed
Read-onlyIdempotent

Generate IBM Granite embedding vectors for one or more texts to index documents and compare meaning for semantic search, RAG retrieval, and similarity scoring.

Instructions

Generate embedding vectors for one or more texts using IBM Granite (default: ibm/granite-embedding-278m-multilingual). Returns one float array per input, suitable for semantic search, RAG retrieval, and similarity scoring. Use this to index documents or compare texts by meaning; it returns vectors, not prose, so call ibm_granite_chat when you need a written answer. Up to 64 texts per call. No IBM Cloud account required — pay $0.005 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": {
      "inputs": "<inputs>"
    },
    "name": "ibm_granite_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOverride the embedding model id (e.g. ibm/granite-embedding-125m-english). Defaults to ibm/granite-embedding-278m-multilingual.
inputsYesTexts to embed. 1–64 strings per call, up to 8,000 characters each.

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.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely non-structured behavior: a 64-text batch ceiling and a per-call price of $0.005 USDC via x402 with no IBM Cloud account needed. What it omits is less critical for an idempotent read—no latency, rate-limit, or partial-failure behavior—so it earns a 4 rather than 5.

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?

Three tight sentences with the purpose and return shape front-loaded, followed by the sibling routing rule and the payment note. The default model id is repeated from the schema, a minor redundancy, but every other clause carries operational information.

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?

With no output schema, the description carries the return-value burden and does so precisely: one float array per input. Combined with the batch cap, cost model, and sibling alternative, an agent has everything needed to call this correctly on the first attempt.

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 both parameters (inputs, model) are already fully documented including the 1–64 range and 8,000-character limit. The description's restatement of "up to 64 texts per call" adds no meaning beyond the schema, and it says nothing about output dimensionality or vector length per model, so it sits at the baseline.

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 opens with a specific verb and resource ("Generate embedding vectors ... for one or more texts") plus the concrete backing model and default. It explicitly distinguishes itself from ibm_granite_chat by stating it returns vectors, not prose, so an agent can route without opening either schema.

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 names concrete use cases (semantic search, RAG retrieval, similarity scoring, indexing documents) and gives an explicit when-not plus the alternative: call ibm_granite_chat when a written answer is needed. That is a clear selection rule, not an inference.

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