Findabis

Get one brand in full

get_brand

Read-onlyIdempotent

One brand in full: location, website, its listed products and FAQs. Example: {"slug":"tilray"}

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	Page slug.

Output Schema

Name	Required	Description
`url`	Yes
`faqs`	Yes	The page's own FAQs, at most five; an answer is marked AI-assisted when the page labels it so
`kind`	Yes
`name`	Yes
`slug`	Yes
`brand`	No
`clinic`	No
`strain`	No
`pharmacy`	No
`description`	Yes
`descriptionAiAssisted`	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

B3.4/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 safety is covered structurally. The description adds that the payload includes location, website, products and FAQs, which is useful expectation-setting, but it says nothing about what happens for an unknown slug (empty result vs error).

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?

Two short sentences, front-loaded with the core statement and followed only by a concrete example. Nothing is redundant or padded.

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?

For a one-parameter read tool with full schema coverage, annotations and an output schema, the essential contract is covered. Missing are the not-found/failure behavior and any routing cue against find_brands, which leaves a small but real gap for an agent choosing between sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented there, so the baseline is met automatically. The inline example {"slug":"tilray"} goes beyond the schema by showing a concrete identifier value for a brand, which helps the agent construct a valid call rather than guessing at slug format.

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?

"One brand in full" combined with the enumerated contents (location, website, products, FAQs) makes the resource and the returned shape clear. The verb is implied rather than stated, and nothing distinguishes it from the adjacent find_brands sibling, but the singular "one brand" versus a search/list tool is inferable.

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 statement or mention of find_brands as the alternative for discovery. The example object hints at how to call it, but not the conditions that should select this tool over its siblings.

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.