Skip to main content
Glama

BlockSentient directory tools

Compare products

compare_products
Read-onlyIdempotent

Returns 2 to 4 products side by side with the same fields for each: plans and prices, documented compliance, transparency and data rights, CTI score with its breakdown, date checked, official site and visit link.

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": {
      "ids": "<ids>"
    },
    "name": "compare_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value by disclosing the exact returned fields (plans/prices, compliance, transparency and data rights, CTI score with breakdown, date checked, official site, visit link), which is meaningful output context. It stops short of saying what happens with an unknown or duplicate id.

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 with no filler; the core action comes first and the field list follows. The field enumeration is slightly run-on but every item conveys what the comparison returns.

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?

With no output schema, the description correctly spends its budget describing the return shape, which is the main gap it needed to fill for a read-only comparison tool. Only the id format and invalid-id behavior are left unaddressed.

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 0%, so the description must carry parameter meaning, and it only echoes the 2-to-4 count constraint already enforced by minItems/maxItems. It never explains what an id actually is (slug, numeric identifier, product name) or how invalid ids 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?

The description gives a specific verb and resource ('Returns 2 to 4 products side by side') and enumerates the compared fields, so an agent knows exactly what comes back. It does not explicitly contrast itself with siblings like get_product or search_products, which is the only thing keeping it from 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 Guidelines3/5

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

Usage is only implied: the '2 to 4 products' framing signals this is for multi-product comparison rather than single lookup, which hints at when to prefer it over get_product. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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