Skip to main content
Glama

Get Dashboard Getaffiliatestatistics Period From To

hgr_get_dashboard_getaffiliatestatistics_period_from_to
Read-onlyIdempotent

Dedicated HGRApi tool for GET api/Dashboard/GetAffiliateStatistics/{period}/{from}/{to}. This is an explicit tool with a fixed endpoint; it is not a generic endpoint caller. HGRApi functional documentation: Purpose: Provides the GET get affiliate statistics operation in dashboard data. Use when: Use it when a client needs to run the get affiliate statistics operation for dashboard data. Input: [FromRoute] period: ePeriod. [FromRoute] from: DateTime?. [FromRoute] to: DateTime?. Output: Returns the result or applies the effect of the get affiliate statistics operation. Search terms: dashboard getaffiliatestatistics period from to.

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": {
      "period": "<period>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "hgr_get_dashboard_getaffiliatestatistics_period_from_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesHGRApi route parameter to.
fromYesHGRApi route parameter from.
periodYesHGRApi route parameter period.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered elsewhere. The description adds only the boilerplate claim that it is a fixed endpoint rather than a generic caller; the output sentence ("Returns the result or applies the effect") is meaningless for a read operation and no rate limits, auth needs, or data shape are given.

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

Conciseness2/5

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

The text is padded with duplicated boilerplate ("explicit tool with a fixed endpoint; it is not a generic endpoint caller"), a redundant route path, and a trailing "Search terms" line that repeats the name. The useful content — input types — is buried mid-paragraph rather than front-loaded.

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

Completeness3/5

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

With annotations and an output schema present, the bar is moderate, and the description covers the route and parameter types. Still missing are the permissible values of the ePeriod enum and any hint about what the statistics payload contains or how date ranges are interpreted, which are the details an agent would most need.

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?

Schema coverage is nominally 100%, but the schema descriptions are empty boilerplate ("HGRApi route parameter period"). The description's Input section meaningfully upgrades this by revealing that period is of type ePeriod (an enum, though values are not listed) and that from/to are nullable DateTimes bound from the route — information the schema does not convey.

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 does state a verb and resource ("get affiliate statistics" for dashboard data) and identifies the fixed route, but the phrasing is largely a restatement of the generated name. It never distinguishes the tool from close siblings such as hgr_get_affiliate_dashboard or hgr_get_affiliate_dashboard_monthly, so an agent cannot choose between them from this text alone.

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?

"Use it when: Use it when a client needs to run the get affiliate statistics operation for dashboard data" is circular and adds no decision criteria. No alternatives, exclusions, or preconditions are named despite several affiliated dashboard tools existing in the sibling list.

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.