Skip to main content
Glama

Family Fishin Website Discovery

Explain Verified Recommendation

explain_recommendation
Read-onlyIdempotent

Show verified supporting facts and canonical source passages for an active Level 2 recommendation rule.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "explain_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds one genuine behavioral constraint beyond that — the rule must be active and Level 2 — which is useful precondition context, but it does not say what happens when the rule_id is inactive, unknown, or of another level (error vs. empty result).

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?

One sentence, front-loaded with the verb and the payload, with no redundant or filler wording. Nothing needs to be trimmed.

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

Completeness3/5

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

With one parameter, no output schema and strong annotations, the definition is close to adequate: it tells the agent what evidence comes back and the rule-state precondition. It falls short on how to obtain a valid rule_id and on the response shape or failure behavior for inactive rules.

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%, so the single required parameter rule_id is documented nowhere but its type and length bounds. The description never states where a rule_id comes from, its format, or whether it must reference an active rule; it only hints at the active/Level 2 constraint without tying it to the parameter.

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?

States a concrete verb ("Show") and names the returned resources precisely: verified supporting facts plus canonical source passages, scoped to "an active Level 2 recommendation rule." An agent can distinguish this from discovery/search siblings, though the term "Level 2 recommendation rule" is internal jargon that is never defined.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named — notably recommend_fishing_approach, which is presumably where a rule_id originates. The agent must infer the workflow linkage entirely from the word "recommendation" in the name.

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