Skip to main content
Glama

Find articles by clinics and pharmacies

find_provider_articles
Read-onlyIdempotent

Find articles UK clinics and pharmacies publish on their own websites (those in the Findabis MCP programme), by words, newest first. Each names the business and links its page on the business's own site, to cite. Not Findabis guides (find_articles), not medical advice. Example: {"query":"first consultation"}

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_provider_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 10.
queryNoWords in the title or text.
offsetNoRows to skip.

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful behavior beyond that: results are sorted newest first and each result names the business and links its page on the business's own site. It says nothing about pagination behavior or result volume, which is the main remaining gap.

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 core purpose and scope, then exclusions, then an example — a sensible ordering with no filler sentences. The parenthetical '(those in the Findabis MCP programme)' and the double-negative 'Not Findabis guides' phrasing make it slightly denser than necessary.

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?

With an output schema, rich annotations, three fully documented parameters and no required arguments, the description covers what an agent still needs: scope, ordering, citation intent, and the sibling exclusion. Only pagination/result-size behavior is left implicit, which is a minor omission given the schema's limit/offset descriptions.

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 already describes query as 'Words in the title or text', limit with a default of 10, and offset. The description's 'by words' plus the example {"query":"first consultation"} add only marginal meaning, so the baseline of 3 is correct.

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?

States a specific verb and resource (find articles) plus a precise scope: articles published by UK clinics and pharmacies on their own websites within the Findabis MCP programme, ordered newest first. It explicitly separates itself from the sibling find_articles (Findabis guides) and signals a different entity than the singular get_provider_article.

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

Usage Guidelines5/5

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

Gives an explicit exclusion and names the alternative tool: 'Not Findabis guides (find_articles), not medical advice.' The 'to cite' framing also tells the agent the intended use case, so selection between this and find_articles is unambiguous.

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.