Skip to main content
Glama
Sign In

Sip.

by io.sip-it
OverviewDiscussionsAdmin

Search wineries

search_wineries
Read-onlyIdempotent

Search South African wineries listed on Sip by name or wine region. Returns name, region, description, rating and the Sip page URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of wineries to return.
queryNoFree-text search on the winery name.
regionNoWine region name or slug, e.g. 'stellenbosch'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safe, idempotent, closed-world read profile, so the description does not need to repeat that. It adds value by enumerating the returned fields (name, region, description, rating, Sip URL), which matters because there is no output schema, and by scoping the catalog to South African listings on Sip.

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 short sentences with no filler: the purpose and scope come first, then the return contents. Nothing could be removed without losing information.

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 simple three-parameter read-only search, the description covers scope, search dimensions, and returned fields. The only meaningful gap is how results are ordered or paginated when limit is reached, though the schema covers the limit itself.

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%, so all three parameters are documented in the schema itself. The description only restates that searching is by name or region, adding little syntax or format detail beyond what the schema already provides; 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 gives a specific verb and resource, 'Search South African wineries listed on Sip', plus the two search dimensions (name or wine region). It is clear what the tool does but never mentions how it differs from a sibling like get_winery, so an agent must infer the boundary.

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 phrase 'by name or wine region' implies when this tool is appropriate, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as get_winery for single-record lookup. Usage is implied rather than stated.

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

All Sip. 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