Findabis

Read one Findabis article

get_article

Read-onlyIdempotent

Read one Findabis article as plain text, with byline, dates and page link. Members-only articles return the link only. Example: {"slug":"how-to-get-a-prescription"}

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Page slug.

Output Schema

Name	Required	Description
`url`	Yes
`body`	Yes	The article as plain text, at most 6000 characters; the page has the rest
`slug`	Yes
`tags`	Yes
`title`	Yes
`author`	Yes
`excerpt`	Yes
`category`	Yes
`truncated`	Yes
`updatedAt`	Yes
`aiAssisted`	Yes	The page labels it AI-assisted
`publishedAt`	Yes	ISO date the article went live
`readingMinutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / slug / description

Previous value: -"The page slug from a find_* tool or search_directory, e.g. \"green-leaf-clinic\"."New value: +"Page slug."

AddedNov 8, 2026

TDQS

A3.8/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, closed world), yet the description still adds real signal: the return is plain text including byline and dates, and members-only articles degrade to a link only. That partial-result behavior is the kind of edge case an agent needs before calling.

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?

Three compact sentences: what it returns first, the members-only exception second, a call example last. Nothing is padded and the most decision-relevant information 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?

The description plus an existing output schema and full annotation coverage leave little ambiguity for a one-parameter read tool. Remaining gaps are minor: behavior for a nonexistent slug (error vs empty) and how members-only status is determined are not mentioned.

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 single slug parameter is already documented with a pattern and length bounds, so the baseline is 3. The embedded example {"slug":"how-to-get-a-prescription"} makes the slug format concrete, but it largely restates what the regex pattern already encodes.

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 and resource ('Read one Findabis article') plus the returned payload shape (plain text, byline, dates, page link), which clearly separates it from the bulk search sibling find_articles. It never names find_articles explicitly, so the single-vs-list distinction is only implied by 'one'.

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?

Usage is implied rather than stated: 'Read one' plus a slug parameter signals retrieval of a known article, leaving find_articles as the unstated alternative. The members-only caveat is the only conditional behavior spelled out; there is no explicit 'use this when' or 'do not use for' guidance.

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

All Findabis 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.