Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Web Search

venice_web_search

Search the web through Brave, Google, or Exa and return structured results with titles, URLs, snippets, and dates, with optional Zero Data Retention and wallet or API key authentication.

Instructions

Search the web with Brave Search (default, Zero Data Retention), Google Search (proxied and anonymized by Venice), or Exa (Zero Data Retention). Returns structured results with titles, URLs, snippets, and dates. Supports x402 wallet auth (no Venice account needed) and API key.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
search_providerNobrave (default) and exa use Zero Data Retention; google is proxied/anonymized by Venice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • changedInput schema / properties / search_provider / description
      Previous value: -"brave (default) uses Zero Data Retention; google is proxied/anonymized by Venice."New value: +"brave (default) and exa use Zero Data Retention; google is proxied/anonymized by Venice."
    • changedInput schema / properties / search_provider / enum
      Previous value: -[
      -  "brave",
      -  "google"
      -]New value: +[
      +  "brave",
      +  "google",
      +  "exa"
      +]
  2. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / query / maxLength
      Previous value: -500New value: +400
    • addedInput schema / properties / search_provider
      Added value: +{
      +  "description": "brave (default) uses Zero Data Retention; google is proxied/anonymized by Venice.",
      +  "enum": [
      +    "brave",
      +    "google"
      +  ],
      +  "type": "string"
      +}
  3. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare openWorldHint=true and readOnlyHint=false; the description adds substantive context beyond them: the data-retention profile of each provider, the return shape (titles, URLs, snippets, dates), and that x402 wallet auth works without a Venice account. It does not mention cost per search or rate limits, which matters given the non-readOnly flag.

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?

Three sentences, front-loaded with the capability, then the return shape, then auth. Nothing is redundant, though the final auth sentence is compressed to the point of being slightly cryptic about how the two auth modes are selected.

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?

With no output schema, the description correctly spells out the return fields, and it covers provider choice and auth. It leaves a gap around result volume/pagination and per-call cost, which an agent spending wallet funds would want to know, but overall it is adequate for a three-parameter read tool.

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 only 33%, and the only schema-described parameter is search_provider, whose description the tool text largely repeats. The description says nothing about what `limit` bounds (1-20) or the `query` length cap of 400 characters, so it does not compensate for the coverage gap; baseline 3 applies.

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 ('Search the web') and enumerates the three backing providers, so the agent knows exactly what the tool does. It stops short of naming the closest sibling, venice_web_scrape, so the search-vs-scrape distinction must be inferred from the verb alone.

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 a default provider ('Brave Search (default)') and the privacy tradeoffs that would drive provider selection, which is real selection guidance. However, it never states when to reach for this tool versus venice_web_scrape, nor any exclusion or prerequisite conditions, so usage is only implied.

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