RetailHardHat

Get Task Trends

get_task_trends

Read-onlyIdempotent

Use this when working with RetailHardHat reports records in the connected organization. Read organization reporting data; no platform-level analytics. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds organization-level scope and notes that MCP approval requirements may be configured by an administrator, which is useful context, but it does not clarify data freshness, aggregation behavior, or what 'task trends' actually covers.

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

Conciseness3/5

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

The description is short and not bloated, but it is not front-loaded with the actual action or resource. The opening phrase 'Use this when working with RetailHardHat reports records' is awkward and buries the core behavior behind context.

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?

Although an output schema exists and no parameters need explanation, the description fails to state the tool's central purpose: retrieving task trends. With many sibling reporting and trend tools available, this omission leaves a significant gap in helping an agent choose and invoke it correctly.

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 input schema has zero parameters, so there is no parameter semantics burden beyond confirming the tool is parameterless. The description does not need to document parameters, and the empty schema is consistent with that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says to read organization reporting data and excludes platform-level analytics, which gives a vague purpose. It never mentions task trends specifically, so an agent must rely on the tool name to infer that this returns task trend reporting rather than bid trends or general report metrics.

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

Usage Guidelines3/5

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

It offers a broad trigger ('Use this when working with RetailHardHat reports records') and a scope exclusion ('no platform-level analytics'), which implies when to use it. However, it does not name alternatives such as get_bid_trends or get_report_metrics, so routing among sibling reporting tools is left to inference.

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

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