Skip to main content
Glama

The Very Lab

Search the website

search_site
Read-onlyIdempotent

Full-text search over the public pages and blog articles of theverylab.com. Returns titles, URLs and short excerpts.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch words, for example: minimum order quantity

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description need not restate that. It does add real value by scoping the index (public pages plus blog articles) and by stating the return shape. It omits result caps, pagination, and ranking behavior, which keeps it short of full transparency.

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?

Two sentences, no filler: the operation and corpus come first, the return value second. Every clause carries information an agent needs.

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 one-parameter, read-only search tool with no output schema, the description covers scope and return contents adequately. Only result volume and pagination behavior are left unstated, a minor gap at this complexity level.

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 100% and the single query parameter already carries its own example, so the description only needs to confirm that free-text keywords (not a URL or ID) are expected. That it does implicitly via 'full-text search,' but adds no syntax guidance such as phrase or operator support; baseline 3 applies.

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

Purpose5/5

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

Names a specific operation (full-text search) over a specific corpus (public pages and blog articles of theverylab.com), and adds what comes back (titles, URLs, excerpts). This clearly separates it from siblings like get_page (fetch a known page) or get_company_profile, so an agent can choose without opening the schema.

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: an agent can infer this is the tool for discovering pages when it lacks a URL. There is no explicit statement of when to prefer it over get_page or the other siblings, and no exclusions or prerequisites are given.

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