Skip to main content
Glama
Sign In

Findabis

by com.findabis
OverviewDiscussionsAdmin

Find Findabis articles

find_articles
Read-onlyIdempotent

Find Findabis articles (UK law, prescriptions, clinics, products) by words or category, newest first. Example: {"query":"travel abroad"}

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

Input Schema

NameRequiredDescriptionDefault
sortNoDefault newest.
limitNoDefault 10.
queryNoWords in the title or text.
offsetNoRows to skip.
categoryNoCategory slug.

Output Schema

NameRequiredDescriptionDefault
totalYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"A blog category slug, as an earlier answer gave it, e.g. \"guides\"."New value: +"Category slug."
    • changedInput schema / properties / limit / description
      Previous value: -"How many to return, 1-25. Default 10."New value: +"Default 10."
    • changedInput schema / properties / offset / description
      Previous value: -"Skip this many results, for the next page (the answer says which offset comes next). Default 0."New value: +"Rows to skip."
    • changedInput schema / properties / query / description
      Previous value: -"Words to look for in the title or text. Omit to browse."New value: +"Words in the title or text."
    • changedInput schema / properties / sort / description
      Previous value: -"newest (default) or oldest first."New value: +"Default newest."
  2. Added

TDQS

B3.2/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 closed-world behavior, so the safety profile is covered. The description's only extra behavioral claim is the 'newest first' default ordering, which is already stated in the sort parameter's schema description, so little value is added beyond structured fields.

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?

A single front-loaded sentence plus a compact example; nothing is padded. The example is slightly redundant with the schema's query description but is not wasteful enough to penalize heavily.

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?

The tool is a simple paginated search with an output schema and full annotations, so much of the burden is carried elsewhere. However, the description omits how to retrieve full article content (get_article) and gives no hint about valid category slugs, leaving notable gaps for an agent planning a search-then-fetch flow.

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 description coverage is 100%, so all five parameters are already documented, including defaults for sort and limit and the category slug pattern. The description adds only a loose mapping ('by words or category') and one example query, which is marginally useful but does not extend semantics beyond the schema.

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 ('Find Findabis articles') and scopes the corpus with examples of content types (UK law, prescriptions, clinics, products). It is clear what the tool does, though it does not explicitly differentiate itself from the singular get_article sibling or from search_directory.

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?

There is no explicit when-to-use guidance and no named alternatives. An agent must infer that this is a keyword/category search over articles versus get_article for fetching a single article, and versus search_directory or the other find_* tools for other entity types.

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

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

Resources