Skip to main content
Glama
Sign In

Findabis

by com.findabis
OverviewDiscussionsAdmin

Search the whole directory

search_directory
Read-onlyIdempotent

Search clinics, pharmacies, products, strains, brands and articles at once, when the kind is unknown or to get a slug. Each match has a kind, slug, URL and one-line summary. Example: {"query":"Glasgow"}

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": {
      "query": "<query>"
    },
    "name": "search_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPer kind. Default 8.
queryYesA name, town or postcode.

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Most results per kind, 1-20. Default 8."New value: +"Per kind. Default 8."
    • changedInput schema / properties / query / description
      Previous value: -"What to look for: a name, brand, strain, town or postcode."New value: +"A name, town or postcode."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description does not need to restate safety. It adds real value by disclosing the result shape ('Each match has a kind, slug, URL and one-line summary'), which tells the agent what a match contains and why slugs are useful for follow-up. It does not discuss result ordering or what happens with zero matches.

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 short sentences, front-loaded with purpose, then result shape, then a minimal example. Nothing is redundant with the annotations or schema in a wasteful way, and the example is compact.

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

Completeness5/5

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

With an output schema present, a fully documented two-parameter schema, and rich annotations, the description only needs to establish purpose, routing, and match shape, all of which it does. Nothing an agent needs in order to select and call this tool is missing.

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%, documenting that query is a name/town/postcode and that limit is per-kind with a default of 8, so the schema carries the weight. The description adds only a worked example ({"query":"Glasgow"}), which illustrates input style but no new semantics; 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?

The description opens with a specific verb ('Search') applied to an enumerated resource set (clinics, pharmacies, products, strains, brands, articles) and the phrase 'at once' signals it spans what the sibling find_* tools cover individually. It stops short of naming a sibling, so differentiation is implied rather than explicit.

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

Usage Guidelines4/5

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

'when the kind is unknown or to get a slug' gives concrete conditions for choosing this over the per-kind find_* tools and the get_* tools, which is the key routing decision. No when-not conditions or explicit sibling names are given, but the context is unambiguous.

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