Skip to main content
Glama
Sign In

WhichPost

by app.whichpost
OverviewDiscussionsAdmin

Compare creators

compare_creators
Read-onlyIdempotent

Two to five creators side by side (paying users, cost per paying user and revenue so far, each with its range, and their decisions), and whether their ranges are far enough apart to tell which one is cheaper yet.

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": {
      "creators": "<creators>"
    },
    "name": "compare_creators"
  }
}

Input Schema

NameRequiredDescriptionDefault
creatorsYes
report_idNoA report id from list_campaigns. Leave out for the newest report.

Output Schema

NameRequiredDescriptionDefault
verdictNo
creatorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds real behavioral value by disclosing what is computed: paying users, cost per paying user, revenue with ranges, decisions, and a statistical separability check.

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?

A single dense sentence, front-loaded with the resource and scope, with no filler. It is slightly run-on but every clause carries meaning about what is compared.

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 values need not be re-explained, and annotations cover the safety profile. The description covers inputs and the comparison semantics adequately, leaving only minor gaps around creator identification format.

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 50% (report_id is documented, the creators array items are not). The description reinforces the 2-5 creator count consistent with schema bounds but adds no new detail on how creators are identified or how report_id interacts. Baseline 3 given partial coverage.

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 states a specific verb+resource (compare 2-5 creators side by side) and enumerates the compared metrics and the differentiating judgment about ranges. It is clear what the tool does, though it does not explicitly name sibling tools like explain_creator or list_creators to sharpen the distinction.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, and no alternatives are named. An agent must infer that this is the multi-creator comparison path versus the single-creator explain_creator or the listing list_creators.

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

All WhichPost toolsInspect
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