Skip to main content
Glama
Sign In

venumark

by com.venumark
OverviewDiscussionsAdmin

search

Alias of search_vendors for ChatGPT Deep Research connectors. Returns matching Florida food vendors as results with id, title, and url. Pass the id to fetch for the full record.

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

Input Schema

NameRequiredDescriptionDefault
queryYesBusiness name, license number, or Florida city

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It states the tool returns results with id, title, and url, implying a read operation. However, it does not explicitly confirm it is read-only, mention authentication needs, rate limits, or any side effects. The alias hint adds some context but leaves gaps.

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 two sentences long, each sentence serving a distinct purpose: first explains the alias and context, second describes the output and next steps. No excess words, and it is front-loaded with the primary purpose.

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?

Given no output schema, the description covers the return format (id, title, url) and the follow-up action (use fetch for full record). It provides sufficient context for basic usage. However, it lacks details on pagination, error handling, or what constitutes a 'match', but for a simple alias tool this is adequate.

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% for the single parameter 'query', which describes acceptable inputs. The description adds context about what the results contain but does not enhance the parameter meaning beyond the schema. Baseline score 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?

Description clearly states it is an alias of search_vendors for ChatGPT Deep Research connectors and returns matching Florida food vendors. The verb 'search' and resource 'vendors' are explicit. However, it does not distinguish itself from the sibling 'search_vendors' beyond being an alias, and the title is null.

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?

The description mentions it is for ChatGPT Deep Research connectors, providing a usage context, and advises passing the id to fetch for the full record. However, it does not explicitly state when to use this tool versus alternatives like 'search_vendors' or 'fetch', nor does it mention any prerequisites or scenarios to avoid.

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

All venumark toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources