WhichPost

Is WhichPost a fit?

check_fit

Read-onlyIdempotent

A quick, fixed questionnaire: from the revenue source, creators per month, new sign-ups or installs a day and a few yes/no answers, it says whether WhichPost is a good fit now, which plan suits, and the next step. The same answers always give the same result; answers are not stored. Needs no sign-in.

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": "check_fit"
  }
}

Input Schema

Name	Required	Description
`apps`	No	How many apps or products.
`is_agency`	No	Whether this is an agency running creators for clients.
`revenue_source`	No	Where the product's payments are recorded. 'none' if it has no payments yet.
`spark_ads_only`	No	Whether the campaign runs only as TikTok Spark Ads.
`creators_per_month`	No	How many creators the team pays for posts in a typical month.
`new_signups_per_day`	No	New sign-ups, trials or installs on a typical day.
`has_paying_customers`	No	Whether the product already has paying customers.
`history_days_before_campaign`	No	Days of sales history before the campaign's first post.

Output Schema

Name	Required	Description	Default
`reasons`	No
`verdict`	Yes
`next_step`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds value beyond that: answers are not stored (privacy), no sign-in required (auth), and same answers always yield the same result (determinism). It doesn't cover rate limits or latency, so it is not a full 5.

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, but it is front-loaded with the tool's nature (quick, fixed questionnaire) before the inputs and outputs. Every clause carries information about inputs, outputs, or behavior, though the sentence is long and could be split for readability.

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 did not need explaining, yet the description still summarizes them. Combined with annotations covering the safety profile and the schema covering inputs, the definition is nearly self-sufficient; only explicit sibling routing is missing.

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%, so the meaning of all 8 inputs is already documented in the schema. The description paraphrases a few of them (revenue source, creators per month, new sign-ups per day, yes/no answers) without adding format, units, or edge-case semantics. Baseline 3 is appropriate.

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 names a concrete resource and outcome: a fixed questionnaire that returns a fit verdict, a recommended plan, and the next step. An agent can tell this apart from informational siblings like about_whichpost or get_pricing. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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?

It gives a clear use context — evaluating whether WhichPost is a good fit right now and which plan suits — which is enough for an agent to invoke it at the right moment. It does not name when NOT to use it or point to an alternative tool (e.g. get_pricing for pure price questions), so no explicit exclusion guidance.

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

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