Skip to main content
Glama

BlockSentient directory tools

Search products

search_products
Read-onlyIdempotent

Finds published products in this directory by words in their name, category, tagline, use case and features. Products that match every word come first, then products that match the rarer half or more of the words, each labelled with the words it matched. Optional: a category, criteria the vendor must document (from the CTI breakdown, e.g. sso, soc2, freeTrial, publicPricing), a minimum CTI score, the order (relevance, name or cti) and an offset for the next page. Returns up to 20 results with ID, name, category, CTI score and grade, the date the facts were checked and the review address. Results are matches, not a ranking or a recommendation.

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": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance needs query words; without them the order is by namerelevance
limitNo
matchNobest: every-word matches first, then partial ones; all: only products matching every wordbest
queryNoWords to look for, e.g. 'invoice approval'
offsetNo
min_ctiNo
categoryNoOptional category ID or name (see list_categories)
documentedNoOnly products whose CTI breakdown gives points for each of these criteria

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only, closed-world annotations, it discloses the two-stage matching behavior, the partial-match threshold, matched-word labels, offset pagination, the 20-result maximum, and the principal returned fields. It also clarifies how results should be interpreted, which is meaningful behavioral context rather than a repetition of the annotations.

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 front-loads the purpose, then logically covers matching, optional controls, output, and interpretation. It is dense, but each sentence contributes operational information and there is no promotional or redundant filler.

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 an eight-parameter search tool with no output schema, the description covers the scope, matching semantics, filters, ordering, pagination, result cap, returned fields, and an important caveat about recommendations. Together with the schema's defaults, enums, and constraints, it provides enough information to invoke the tool and interpret its results correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 63% schema coverage, the description adds substantial meaning: it explains where query words are searched, how partial matching works, what documented CTI criteria represent, and how offset is used. Some operational details remain schema-only or are not explicitly tied to parameter names, particularly the match modes, default limit and sort behavior, and category ID/name handling.

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 opening sentence gives a specific verb, resource, scope, and searchable fields: finding published directory products through words in names, categories, taglines, use cases, and features. This clearly establishes keyword search, but it does not explicitly distinguish the tool from siblings such as get_product or compare_products.

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

Usage Guidelines4/5

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

The description supplies clear usage context through keyword search, optional category and CTI filters, sorting, and pagination. The closing statement that results are matches rather than a ranking or recommendation is a useful limitation, but there is no explicit routing to another tool for product details, comparisons, or recommendations.

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