Skip to main content
Glama

Family Fishin Website Discovery

Evidence-Verified Fishing Approach

recommend_fishing_approach
Read-onlyIdempotent

Return only active recommendations supported by verified facts and published source passages. Empty recommendations are intentional when evidence is insufficient.

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

Input Schema

NameRequiredDescriptionDefault
questionYes
max_rulesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, and the description still adds genuinely non-obvious behavior: results are evidence-gated and may legitimately be empty. It omits what a returned recommendation looks like and gives no indication of cost or latency, which keeps it short of a 5.

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

Conciseness4/5

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

Two tight sentences with zero filler, and the evidence-gating constraint is front-loaded where it matters most. It is efficient but arguably under-sized for a tool with an undocumented 2-parameter surface.

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?

With no output schema and zero schema coverage, the description is the only documentation an agent gets, and it leaves the return shape undefined beyond the word 'recommendations'. For an open-world tool that caps results via max_rules and may return empty, the definition does not supply enough for confident invocation.

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% across two parameters, so the description must carry the meaning, and it says nothing about either one. Neither the 'question' input (length limits, expected phrasing, whether natural language or keywords) nor 'max_rules' (the fact that it caps returned rules, range 1-10, default 5) is explained anywhere.

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 gives a specific verb-and-object ('Return only active recommendations') but never states the domain or framing the tool operates on — the word 'fishing' appears only in the name and title. It is not pure tautology because it adds evidence-verification and empty-result semantics, but an agent cannot tell from this text how it differs from siblings like get_fishing_guidance or explain_recommendation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and none of the sibling tools are named as alternatives. The line about empty recommendations is a behavioral expectation about results, not a routing rule that tells an agent when to pick this tool over analyze_fishing_conditions or search_fishing_knowledge.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources