Skip to main content
Glama

Read one clinic or pharmacy article

get_provider_article
Read-onlyIdempotent

Read one article a UK clinic or pharmacy published on its own website, as plain text, with the business, dates and the page on its site to cite. The business's view, not Findabis's. Example: {"slug":"what-happens-at-your-first-consultation"}

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_provider_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPage slug.

Output Schema

NameRequiredDescriptionDefault
urlYesThe article's page on the business's own website: cite this
bodyYesThe article as plain text, at most 6000 characters; the page has the rest
slugYes
titleYes
excerptYes
providerYes
truncatedYes
updatedAtYes
aiAssistedYesThe business labels it AI-assisted
publishedAtYesISO date the article went live
readingMinutesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / provider / properties / directoryUrl / $ref
      Removed value: -"#/properties/excerpt"
    • addedOutput schema / properties / provider / properties / directoryUrl / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / readingMinutes / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": -9007199254740991,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / updatedAt / $ref
      Removed value: -"#/properties/excerpt"
    • addedOutput schema / properties / updatedAt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Added

TDQS

A3.9/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 and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: output is plain text and includes the business, dates, and the source page to cite, which matters for attribution-sensitive use.

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?

Front-loaded with the verb and scope, then the differentiator, then what comes back. The embedded JSON example is compact but slightly redundant against a fully documented schema; nothing else is wasted.

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?

An output schema exists, so return values need not be enumerated, and the description still sketches them briefly. The one real gap is not telling the agent where a valid slug comes from, presumably find_provider_articles, which matters for a required identifier.

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% with a single required slug already constrained by pattern and length, so the schema does the heavy lifting. The inline example restates a valid slug shape but adds no meaning beyond the pattern, making baseline 3 appropriate.

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

Purpose5/5

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

Specific verb (read) plus a narrowly scoped resource: one article a UK clinic or pharmacy published on its own website. The phrase 'The business's view, not Findabis's' explicitly separates it from sibling get_article, so an agent can route without opening either schema.

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 by the contrast with Findabis-authored content, which tells the agent this is the provider-authored variant, but no alternative tool is named and no condition for choosing between get_article and get_provider_article is spelled out. The agent must infer the split from the sibling names.

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.