Skip to main content
Glama
Sign In
PostKing MCP Server

PostKing MCP Server

by bitsandtea
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

competitor_recompute_comparison

Recompute head-to-head competitor comparisons after adding or re-analyzing competitors to get up-to-date results.

Instructions

Trigger a fresh head-to-head comparison recompute. Use after adding or re-analyzing competitors to get an up-to-date comparison.

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

Input Schema

NameRequiredDescriptionDefault
brandIdNoBrand ID (defaults to active brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.7

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral transparency. It hints at an asynchronous action ('Trigger') but fails to disclose whether it blocks, returns immediately, or requires polling for completion. It also omits potential side effects like overwriting existing comparisons.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, direct and front-loaded. Every word earns its place with no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and no annotations, so the description must explain outcomes and next steps. It explains purpose and trigger conditions but leaves the agent guessing about how results are obtained, whether the operation is asynchronous, and what 'recompute' entails. This is a significant gap for a tool with no other context.

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?

The input schema fully documents the only parameter (brandId) with a description, so baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already provides, but it doesn't need to compensate given high schema coverage.

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 uses a specific verb ('Trigger') and a clear object ('fresh head-to-head comparison recompute'), making the tool's purpose unmistakable. It also distinguishes itself from read-only comparison tools by emphasizing the recompute action.

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 description explicitly states when to use this tool ('after adding or re-analyzing competitors') and the intended goal ('to get an up-to-date comparison'). It does not name alternative tools, but the usage context is sufficiently clear.

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

Deploy Server

Other Tools