Skip to main content
Glama

Visibility Genies

Read the knowledge base

get_knowledge_base
Read-only

Reads what Visibility Genies keeps about the project's business and own website: the business memory by block (company, offers, audience, proof points, goals, positioning, voice, rules, notes and more), each entry with its short id, its state (Confirmed, or proposed by the AI, an assistant, Search Console, Analytics or a review) and its source, and the pages its site audit crawled, 50 at a time, each with its type, words and summary. Free. Read it before writing about the site.

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>"
    },
    "name": "get_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich 50 pages to list, from 0.
pageTypeNoOnly pages of this type.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
baseYes
metaNo
pagesYes
totalYes
needsJavaScriptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: pagination of 50 items at a time, and that entries carry a state (Confirmed vs. proposed by AI, an assistant, Search Console, Analytics or a review) and a source, which warns the agent that some content is machine-proposed rather than verified. It does not describe ordering, whether proposed entries can be filtered, or size limits on total retrievable blocks.

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 verb and content scope, followed by the payload detail and the actionable 'Free. Read it before writing about the site.' The long parenthetical block list ('company, offers, audience, proof points, goals, positioning, voice, rules, notes and more') is dense but sets expectations about what comes back; overall it is a single well-ordered paragraph with little waste.

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 present, return values need not be explained, yet the description still previews the shape (blocks, entries with id/state/source, crawled pages with type, words, summary) and states the paging increment. For a 3-parameter read tool with full annotations this is sufficient; only the handling of unconfirmed entries when writing about the site is left implicit.

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%, so the schema already documents projectId, page and pageType including the enum values. The description only restates the '50 at a time' batching, which the page parameter description already conveys, and adds nothing about pageType filtering or paging limits 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?

Specific verb + resource: "Reads what Visibility Genies keeps about the project's business and own website", then enumerates the content blocks (company, offers, audience, proof points, goals, positioning, voice, rules, notes) plus crawled pages. It is clearly distinguishable from a search or update operation in substance, though it never names the sibling read/write tools, so differentiation rests on inference from the described scope.

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?

Gives an explicit trigger: "Read it before writing about the site", plus a cost signal ("Free.") that favors calling it. It offers no exclusion conditions and does not route the agent to search_knowledge_base for lookups or update_knowledge_base for writes, so it is clear context without alternatives.

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