Skip to main content
Glama
pzehrel

tavily-proxy-mcp

by pzehrel

tavily_search

Read-only

Search the web for current information on any topic, returning snippets and source URLs. Get news, facts, or data beyond your knowledge cutoff.

Instructions

Search the web for current information on any topic. Use for news, facts, or data beyond your knowledge cutoff. Returns snippets and source URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query
topicNoThe category of the search. This will determine which of our agents will be used for the searchgeneral
countryNoBoost search results from a specific country. Must be a full country name (e.g., 'United States', 'Japan', 'Germany'). ISO country codes (e.g., 'us', 'jp') are not supported. Available only if topic is general. See https://docs.tavily.com/documentation/api-reference/search for the full list of supported countries.
end_dateNoWill return all results before the specified end date. Required to be written in the format YYYY-MM-DD
start_dateNoWill return all results after the specified start date. Required to be written in the format YYYY-MM-DD.
time_rangeNoThe time range back from the current date to include in the search results
exact_matchNoOnly return results containing the exact phrase(s) in quotes in your query
max_resultsNoThe maximum number of search results to return
search_depthNoThe depth of the search. 'basic' for generic results, 'advanced' for more thorough search, 'fast' for optimized low latency with high relevance, 'ultra-fast' for prioritizing latency above all elsebasic
include_imagesNoInclude a list of query-related images in the response
exclude_domainsNoList of domains to specifically exclude, if the user asks to exclude a domain set this to the domain of the site
include_domainsNoA list of domains to specifically include in the search results, if the user asks to search on specific sites set this to the domain of the site
include_faviconNoWhether to include the favicon URL for each result
include_raw_contentNoInclude the cleaned and parsed HTML content of each search result
include_image_descriptionsNoInclude a list of query-related images and their descriptions in the response

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, and non-destructive behavior. The description adds the return format ('Returns snippets and source URLs'), which is useful behavioral context beyond annotations. It doesn't mention rate limits or pagination, but given the annotation coverage, this is acceptable.

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 is three concise sentences that are front-loaded with the core purpose. Key usage guidance and return format are included without unnecessary verbosity. Every sentence earns its place.

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?

With a rich output schema and 100% parameter documentation, the description doesn't need to explain return values or parameters. It provides the essential purpose, usage context, and behavioral output format, making it complete for tool selection and invocation.

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 all 15 parameters are documented in the schema. The description itself adds no parameter-level meaning beyond what's already in the input schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states 'Search the web for current information on any topic' with a specific verb and resource. It also mentions usage for 'news, facts, or data beyond your knowledge cutoff,' which gives context but doesn't explicitly differentiate from sibling tools like tavily_extract or tavily_research.

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 provides clear guidance on when to use this tool: 'Use for news, facts, or data beyond your knowledge cutoff.' It doesn't specify exclusions or alternatives, but the context is clear enough for an agent to understand when web search is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pzehrel/tavily-proxy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server