search_merchants
Locate merchants at Ohio State University using their name or category.
Instructions
Search for merchants by name or category
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search term for merchant name or category |
Locate merchants at Ohio State University using their name or category.
Search for merchants by name or category
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search term for merchant name or category |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description lacks behavioral details such as read-only nature, number of results, pagination, or search algorithm (exact vs fuzzy). Minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no fluff. Efficient but could be slightly more detailed without losing conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a search tool with no output schema or annotations, the description should explain behavior (e.g., result format, limits, search type). It is incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the only parameter 'query' is described in the schema. The tool description adds no additional meaning beyond what is already in the schema, so baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool searches for merchants by name or category, with a specific verb and resource. It distinguishes from sibling tools like get_merchants_by_food_type and get_buckid_merchants.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives. No mention of when not to use or context for preferring search_merchants over other merchant-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sichengchen/ohio-state-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server