Family Fishin Website Discovery

Automatically Route a Public Fishing or Tackle Question

answer_public_question

Deterministically retrieve source-grounded educational evidence, live read-only catalog data, or both when a question requires multiple sources. No generative AI or purchases.

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": {
      "question": "<question>"
    },
    "name": "answer_public_question"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`question`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- changedInput schema / properties / question / maxLength
```
Previous value: -1200New value: +12000
```
AddedNov 6, 2026

TDQS

C2.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose useful traits ('deterministically', 'no generative AI', 'no purchases', read-only catalog access). However, it omits the domain scope (the title says public fishing/tackle, the description does not), what is returned (evidence vs. answer vs. products), and any limits or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, but the lead clause is dense nominal phrasing ('Deterministically retrieve source-grounded educational evidence') that buries the actionable meaning. The constraint sentence ('No generative AI or purchases') is the clearest part and would work better front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and fully undocumented parameters, the description is insufficient: it doesn't establish what the caller receives, how the returned sources are shaped, or how the returned data should be cited or combined. Only the negative constraints and determinism are adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% on two parameters, and the description supplies no meaning for either. The 'question' parameter's role is only inferable from its name, and the 'limit' parameter (1-10, default 5) is entirely unexplained — e.g., whether it caps evidence items, catalog items, or both.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resources ('source-grounded educational evidence, live read-only catalog data') but never says the tool answers or routes a user question, and the phrasing is abstract jargon rather than a concrete verb+resource. It gives no signal distinguishing it from siblings like search_fishing_knowledge or search_products, which appear to retrieve the same underlying data.

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?

'when a question requires multiple sources' is an implicit selection condition that hints at single-source alternatives, but no sibling is named and no exclusion or preconditions (e.g., domain, authentication) are stated. An agent must still infer when to prefer this over the search_* tools.

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

All Family Fishin Website Discovery tools Inspect

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

Need Help?