Skip to main content
Glama

Visibility Genies

Read the client report

get_client_report
Read-only

The project's client report as its client would read it, the same one Project settings previews: the Summary's five answers, the scores and what changed, the actions done so far this calendar month (period, in UTC) and the next ones, and the ad results where an ad account is connected, as of today. Read it to write a monthly report; send nothing to a client without the user's review. Creates no link: create_report_share does that, only when the user asks. Free: it reads saved data and buys nothing.

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

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
asOfYes
metaNo
periodYes
reportYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false; the description goes further by defining the reporting period ('calendar month, period in UTC'), the snapshot point ('as of today'), the conditional dependency for ad results ('where an ad account is connected'), and the cost profile ('Free: it reads saved data and buys nothing'). It also explicitly disclaims the side effect of creating a share link, which prevents a common misassumption.

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?

Content is front-loaded: what the report contains comes first, then the usage warning, then the sibling disclaimer, then the cost note. The single dense paragraph is efficient, though the semicolon-chained clauses make it slightly run-on and harder to scan than bulleted sections would be.

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?

An output schema exists, so return structure need not be spelled out, and the description still summarizes the report contents, period semantics, and conditional sections. For a read-only single-parameter tool with full annotation coverage, nothing an agent needs to invoke it safely is missing.

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?

The single parameter is fully documented in the schema (100% coverage) as required and project-scoped. The description adds routing guidance by naming list_projects as the discovery path, but does not restate the parameter itself, so it adds modest but real value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('The project's client report as its client would read it') and then enumerates the constituent sections: the Summary's five answers, scores and changes, actions this calendar month, upcoming actions, and ad results when an ad account is connected. It also explicitly distinguishes itself from the sibling that creates shares, so an agent can tell it apart without opening another schema.

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

Usage Guidelines5/5

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

It gives an explicit use case ('Read it to write a monthly report'), an explicit constraint ('send nothing to a client without the user's review'), and routes the adjacent capability elsewhere ('Creates no link: create_report_share does that, only when the user asks'). Nothing is left to inference about when this tool is and is not appropriate.

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