Skip to main content
Glama

Family Fishin Website Discovery

Get Family Fishin Article

get_article
Read-onlyIdempotent

Fetch one public Family Fishin WordPress article by numeric ID or slug. Returns cleaned plain text and canonical metadata.

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": {
      "id_or_slug": "<id_or_slug>"
    },
    "name": "get_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_slugYesA WordPress post ID, such as '123', or a post slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds value beyond them by scoping the tool to public articles only and describing the return as cleaned plain text with canonical metadata, which matters since no output schema exists. It omits what happens when the ID or slug is not found.

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?

Two short sentences: identity and scope first, return shape second. No filler, repetition, or hedging, and the key constraint ('public', 'one') is front-loaded.

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

Completeness4/5

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

A single-parameter read tool with no output schema is well served by naming the return payload and public-only scope. The only meaningful gap is error/not-found behavior, which is a minor omission at this complexity.

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

Parameters3/5

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

Schema coverage is 100% and the schema field description already explains that id_or_slug accepts a post ID such as '123' or a post slug. The description restates the same distinction without adding format, ordering, or fallback behavior, so baseline 3 applies.

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 specific verb ('Fetch') and resource ('one public Family Fishin WordPress article') plus the lookup key (numeric ID or slug). It is clear on its own, but it does not distinguish itself from the sibling search_articles or explain that this is the retrieval step after a search.

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?

The description implies usage ('by numeric ID or slug') but gives no explicit when-to-use or when-not guidance, and never names the alternative (search_articles) for agents that don't yet have an ID or slug. An agent must infer the workflow.

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