search_fishSearch fish by name (Japanese, Thai, or English). Provide lineUserId to include VIP tier pricing.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Fish name to search for | |
| lineUserId | No | LINE user ID for VIP pricing (optional) |
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| results | Yes | ||
| vipCompanyName | No | Shown as (VIP: …) when VIP pricing is applied |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "query": {
+ "type": "string"
+ },
+ "results": {
+ "items": {
+ "properties": {
+ "fishName": {
+ "type": "string"
+ },
+ "packs": {
+ "type": "integer"
+ },
+ "priceThbPerKg": {
+ "description": "VIP price (only shown for VIP callers)",
+ "type": "number"
+ },
+ "status": {
+ "type": "string"
+ },
+ "thaiName": {
+ "type": "string"
+ },
+ "tier": {
+ "type": "string"
+ },
+ "weightKg": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "fishName",
+ "tier",
+ "status",
+ "weightKg",
+ "packs"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "vipCompanyName": {
+ "description": "Shown as (VIP: …) when VIP pricing is applied",
+ "type": "string"
+ }
+ },
+ "required": [
+ "query",
+ "results"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: matching works across Japanese, Thai and English names, and supplying lineUserId changes what pricing tier is returned.
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?
Two short sentences with zero filler, and the core capability is front-loaded before the optional-pricing hint. Nothing repeats gratuitously.
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?
With a rich annotation set, full schema coverage and an output schema, the definition covers what matters at this complexity. It stops short of saying whether matching is exact or partial, which would help an agent form queries.
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%, so both parameters are already documented, and the description largely restates them. The one added nuance is that lineUserId affects VIP pricing in the response, which is roughly already implied by the schema text.
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?
States a specific verb and resource (search fish) and adds the searchable name languages. It does not distinguish itself from the closest sibling, get_catalog, so an agent must infer which to reach for.
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?
Usage is implied by the name-search framing, and the lineUserId tip hints at a VIP-pricing variant of the call. There is no explicit when-to-use statement, no exclusion of alternatives like get_catalog, and no prerequisite guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.