Skip to main content
Glama

Visibility Genies

Search the knowledge base

search_knowledge_base
Read-only

Finds the project's own pages that best match a keyword, topic or title, from the text its site audit crawled, with a summary and an excerpt of each. Free. Use it to see whether the site already covers a topic and which page does.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesA keyword, topic or title to find the site's pages about.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
pagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the corpus is the site-audit crawl text rather than live web results, the result includes a summary and excerpt per page, and the call is 'Free' (no credit cost). It does not discuss ranking thresholds or what happens on zero matches, which the output schema would have to cover.

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 compact sentences, front-loaded with the verb and resource, then the return shape, then the decision rule. The one-word 'Free.' sentence is short but carries real billing information an agent cannot get elsewhere.

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 covering the return shape and annotations covering safety, the description only needs to convey corpus, matching semantics and intent — all of which it does. Nothing essential for calling it correctly with projectId and query 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 coverage is 67%, and the description's 'keyword, topic or title' merely restates the query parameter's own schema text. The limit parameter (default 8, max 20) receives no explanation in either the description or the schema, and projectId scoping is handled entirely by the schema description.

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 gives a specific verb ('Finds') and a precisely scoped resource: the project's own pages, drawn from text its site audit crawled, ranked by best match to a keyword/topic/title. That scope distinguishes it from broader retrieval tools, though no sibling (e.g. get_knowledge_base) is named explicitly, so it stops short of the top score.

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?

It states a concrete use case: 'Use it to see whether the site already covers a topic and which page does.' That is clear when-to-use guidance, but there are no when-not conditions and no named alternative for retrieving a known page by ID versus searching by topic.

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.

Resources