Skip to main content
Glama

Visibility Genies

Read project context

get_project_context
Read-only

Reads the project's shared memory: 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; then competitors, key pages, brand names and the research log, and the blocks with nothing yet. Read it before planning work for a project. Free.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
entriesNo
keyPagesYes
sectionsYes
brandNamesYes
competitorsYes
researchLogYes
customSectionsYes
missingSectionsYes
brandCapitalOnlyYes
proposedSectionsYes

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 establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the entry-state model (Confirmed vs AI/assistant/Search Console/Analytics/review-proposed) and the source field tell the agent how to interpret results, and "Free" discloses cost. It still does not mention pagination, size limits, or behavior on an empty project.

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?

Two sentences, front-loaded with the verb and ending with the actionable directive, so nothing is buried. The middle enumeration is long and runs together in one sentence, which makes it denser than needed, but each listed item is informative rather than filler.

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?

An output schema exists, so return-value explanation is technically optional, yet the description still previews the response shape and state semantics, which is more than enough for a single-parameter read tool. The only gap is guidance on large or empty projects, a minor omission given the low complexity.

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% and the single projectId parameter is already documented in the schema with the required flag and the pointer to list_projects. The description adds no meaning beyond that, so the 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?

Opens with a specific verb+resource ("Reads the project's shared memory") and enumerates the contents: business memory blocks by name, entry state, source, competitors, key pages, brand names, research log, and empty blocks. An agent knows exactly what comes back. It stops short of naming a sibling such as get_project_summary, so the read-vs-summarize distinction is only implicit.

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?

"Read it before planning work for a project" gives a concrete trigger condition for use, and the trailing "Free" signals no credit cost, which matters for call ordering. There is no explicit when-not-to-use or pointer to an alternative tool, which keeps it below 5.

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