Skip to main content
Glama

x402-bigram-similarity

Bigram Similarity: Computes Jaccard similarity between word-pair bigrams of texts a and b (or text1 and text2) 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-bigram-similarity"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNo
bNo
text1No
text2No

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / a / description
      Removed value: -"A to process"
    • removedInput schema / properties / b / description
      Removed value: -"B to process"
    • removedInput schema / properties / text1 / description
      Removed value: -"Text1 to process"
    • removedInput schema / properties / text2 / description
      Removed value: -"Text2 to process"
  2. Changed4 schema fields changed
    • addedInput schema / properties / a
      Added value: +{
      +  "description": "A to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / b
      Added value: +{
      +  "description": "B to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / text1
      Added value: +{
      +  "description": "Text1 to process",
      +  "type": "string"
      +}
    • addedInput schema / properties / text2
      Added value: +{
      +  "description": "Text2 to process",
      +  "type": "string"
      +}
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the underlying algorithm (Jaccard over word-pair bigrams) and a pricing/auth signal (free trial calls per signed wallet), which is genuine behavioral context. It omits return format, score range, and error/edge behavior.

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?

A single front-loaded sentence states the operation, and the pricing tag is brief. The promotional emoji/free-trial tail adds little evaluative value but costs almost nothing in length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, 0% schema coverage, and zero required parameters, the description should explain the similarity output (range, format) and input resolution rules. It covers the aliasing hint but leaves the return contract and requiredness entirely unspecified.

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 0% across four undocumented params. The description partially compensates by clarifying that 'a' and 'b' are aliases for 'text1' and 'text2', which resolves real schema ambiguity. It does not state requiredness, whether both pairs may be supplied, or how mismatched inputs are handled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Computes Jaccard similarity between word-pair bigrams'. This distinguishes it from generic similarity tools like x402-jaccard-similarity or x402-string-similarity. However, it never explicitly names a sibling to route against, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative-tool guidance is given. The only conditional context is the pricing note ('5 free trial calls per signed wallet'), which is commercial, not usage-selecting. The agent is left to infer when bigram Jaccard beats other similarity tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources