Skip to main content
Glama
Sign In
Web Search MCP

Web Search MCP

by thehappyboy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

vertical_sub_domains

Inspect a vertical domain to discover its sub-domains and required parameters. Use this tool before vertical_search to obtain the schema.

Instructions

Discover sub-domains and required parameters for a given vertical domain. Call before vertical_search when sub_domain schema is unknown.

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

Input Schema

NameRequiredDescriptionDefault
domainNoSingle domain to inspect (e.g. "finance")
domainsNoComma-separated list of domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description must cover behavior. It implies a read operation ('Discover'), but does not explicitly state it's non-destructive, mention return format, or disclose any side effects or authorization needs.

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, front-loaded with the action verb and resource. No unnecessary words; each sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not clarify return structure (e.g., list of subdomains). It also does not mention handling of multiple domains in 'domains' parameter or relation to other siblings like vertical_batch.

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?

Schema coverage is 100% with parameter descriptions. The description adds value by explaining the purpose of the parameters (discovering sub-domains/params), giving context beyond what the schema provides.

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?

The description clearly states the tool discovers sub-domains and required parameters for a vertical domain, and distinguishes it from the sibling 'vertical_search' by specifying when to call it.

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?

Explicitly says to call before vertical_search when sub_domain schema is unknown, providing good contextual guidance. However, it does not address when not to use the tool or mention other siblings like vertical_batch.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools