WhichPost (public)

Sample report (simulated)

get_sample_report

Read-onlyIdempotent

A labelled sample report built from simulated data, so anyone can see what WhichPost answers before connecting their own data: paying users with their likely range, cost per paying user, and a decision per creator. Needs no sign-in. The numbers are simulated and are not anyone's results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sample_report"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`spend`	No
`checks`	No
`sample`	No
`revenue`	No
`currency`	No
`headline`	Yes
`decisions`	No
`next_step`	No
`report_url`	Yes
`paying_users`	Yes
`revenue_note`	No
`no_clear_effect`	No
`cost_per_paying_user`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive, idempotent, and closed-world behavior, so the bar is lower. The description adds genuinely new context: no authentication is required and the numbers are simulated, not anyone's real results — important provenance an agent must not misreport as real data.

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?

Single front-loaded sentence that leads with what the tool is before elaborating. Slightly redundant — 'simulated data' is restated as 'The numbers are simulated and are not anyone's results' — but the repetition reinforces a critical caveat rather than padding.

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 present and annotations covering the safety profile, the description only needs to establish provenance and access requirements, both of which it does. Nothing needed to call or interpret the tool correctly 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 tool takes zero parameters, so the baseline is 4 and there is nothing further the description could usefully add about argument semantics.

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?

States a specific artifact (a labelled sample report) built from simulated data, and pins down what it contains: paying users with likely range, cost per paying user, and a decision per creator. This distinguishes it cleanly from the sibling get_latest_report, which returns real data.

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?

The phrase 'before connecting their own data' and 'Needs no sign-in' clearly frame the pre-onboarding/demo context in which this tool is appropriate. It stops short of explicitly excluding or contrasting with get_latest_report, but the intended use case is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All WhichPost (public) 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.

Resources

Need Help?