Skip to main content
Glama

get_platform_rejection_trends

Read-only

Check what coaches across the whole platform have been rejecting recently, as category counts (never any client's raw rejection text — this is a general pattern, not client-specific data). Use this as a secondary caution alongside get_client_ai_history, not a hard constraint: if one category is clearly dominant (e.g. over 30% of recent rejections), be a bit more conservative in that area by default, unless this client's own profile or history argues otherwise. This client's own data always takes priority over this platform-wide signal.

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

Input Schema

NameRequiredDescriptionDefault
sinceDaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true) and scope (openWorldHint=false), but the description adds genuinely new behavioral context: the data is aggregated to category counts and never exposes a client's raw rejection text. It does not describe the exact response shape or whether low-volume periods produce noisy counts, which keeps it short of a 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?

Front-loaded with what the tool returns and its privacy boundary, then the usage rule. Slightly redundant: 'unless this client's own profile or history argues otherwise' and 'This client's own data always takes priority' restate the same precedence idea.

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?

For a single-parameter, read-only aggregate tool with no output schema, the description covers purpose, caveats, and precedence well. The one gap is the undocumented time-window parameter, which is left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter sinceDays has 0% schema description coverage, so the description must carry that burden. It offers only the vague word 'recently' and never mentions the lookback window, its default of 30 days, or its 1-90 day bounds, so an agent must open the schema to use it correctly.

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 verb and resource ('Check what coaches across the whole platform have been rejecting recently') plus the output shape ('as category counts') and an explicit privacy boundary ('never any client's raw rejection text'). It is clearly distinguishable from get_client_ai_history, which is named as the client-specific counterpart.

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?

Explicitly frames this as a 'secondary caution alongside get_client_ai_history, not a hard constraint', gives a concrete decision threshold (dominant category over 30% of recent rejections), and states the precedence rule that the client's own data always wins. When-to-use, when-not-to-override, and the alternative are all present.

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.