Skip to main content
Glama

BlockSentient directory tools

Ask this directory a question

ask_site
Read-onlyIdempotent

Answers a plain-language question about this directory's listings, e.g. 'invoice approval tools with SSO and a free trial', with up to 10 matching products as schema.org records (review page, official site, CTI score and a visit link). It is the same answer as the site's NLWeb /ask address. No model runs: the words are matched against the listings, so short questions with the words that matter work best. Results are matches, not a ranking or a recommendation.

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": {
      "query": "<query>"
    },
    "name": "ask_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesThe question, plain text

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 establish read-only, idempotent, closed-world behavior, so the bar is lower; the description still adds substantial context by disclosing that no model runs and the words are keyword-matched against listings. It also previews the return payload (review page, official site, CTI score, visit link) and caps results at 10. The default limit of 5 and pagination/absence handling are not discussed.

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?

Four sentences, front-loaded with the concrete example, and each sentence carries distinct information (capability, endpoint equivalence, matching mechanic, output nature). The NLWeb /ask sentence is the weakest for an agent that only calls MCP, but it is brief.

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?

For a two-parameter, read-only lookup with no output schema, the description covers what is asked, how matching works, how many results come back and roughly what each result contains. Only the default limit and behavior on zero matches are unaddressed, which is a minor gap.

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 50%: 'query' carries a description and 'limit' is documented only by its type bounds. The description compensates partially by stating 'up to 10 matching products,' which explains the ceiling on limit, and the keyword-matching note tells the agent what to put in query. It does not explain the default of 5 or how limit interacts with match count.

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 opens with a specific verb and resource ('Answers a plain-language question about this directory's listings') and concretely illustrates it with an example query, so the agent knows exactly what the tool yields. It stops short of naming a sibling such as search_products to mark the boundary, so differentiation is inferred rather than stated.

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?

It gives real usage guidance of a sort: 'short questions with the words that matter work best' and 'Results are matches, not a ranking or a recommendation.' That tells the agent how to phrase input and how to interpret output, but it never says when to prefer this over search_products or compare_products, which is the more important routing question.

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