Skip to main content
Glama

Ask the website

ask
Read-onlyIdempotent

Retrieve relevant passages from this website's published index using NLWeb v0.55. Query and context together are limited to 2000 characters; prefer.limit accepts 1–20 (default 5).

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

Input Schema

NameRequiredDescriptionDefault
metaNoOptional: request_id (up to 128 characters) becomes the answer's request id. version, when sent, must be 0.55.
queryYesThe question in text, at most 2000 characters together with context. site is optional and must match this website.
preferNoOptional: limit sets how many passages come back (1-20, default 5). Only list mode and the conversational_search format are supported.
contextNoOptional earlier conversation for a follow-up: prev (earlier questions), text and memory. They are searched together with the question.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / context / description
      Added value: +"Optional earlier conversation for a follow-up: prev (earlier questions), text and memory. They are searched together with the question."
    • addedInput schema / properties / meta / description
      Added value: +"Optional: request_id (up to 128 characters) becomes the answer's request id. version, when sent, must be 0.55."
    • addedInput schema / properties / prefer / description
      Added value: +"Optional: limit sets how many passages come back (1-20, default 5). Only list mode and the conversational_search format are supported."
    • addedInput schema / properties / query / description
      Added value: +"The question in text, at most 2000 characters together with context. site is optional and must match this website."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds little beyond what the schema already states: the combined query+context character cap and the limit range/default are restated verbatim from the schema descriptions. It says nothing about result ranking, citation format, or what happens when the index has no match.

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 tight sentence with the core action front-loaded, followed by the two hard constraints. The version string 'NLWeb v0.55' is defensible since meta.version must be 0.55, though it reads slightly like implementation trivia.

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?

An output schema exists, all four parameters are fully documented in the schema, and annotations carry the safety profile. The description only needs to state what the tool does and its hard limits, which it does.

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 the schema already documents query.text, query.site, context.prev/text/memory, meta.request_id and prefer.limit. The description repeats the limit range and the 2000-character cap rather than adding interpretation, so the baseline of 3 is appropriate.

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: retrieve relevant passages from this website's published index. That is far more concrete than the tool name 'ask' and clearly separates it from a feedback-submission sibling, though it never names the alternative explicitly.

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 or when-not-to-use guidance is given; the description never references send_feedback or explains any selection criteria. The only guidance offered is numeric constraints (2000 characters, limit 1-20), not context for choosing or timing the call.

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