Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

list_payouts

Read-onlyIdempotent

Retrieve a page of your payout amounts, currencies, dates, and statuses to review earnings. Use filters and pagination to inspect payout history.

Instructions

Read a page of your personal payout amounts, currencies, dates and statuses. Request this when reviewing earnings.

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

Input Schema

NameRequiredDescriptionDefault
limitNoSource records per request, before local filtering.
offsetNoUse nextOffset from the previous response.
statusIdNo
paidSinceNoUnix timestamp in seconds (UTC).
createdSinceNoUnix timestamp in seconds (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered and the description needn't repeat it. The description adds that results are paged and personally scoped, but says nothing about page-size behavior, ordering, or how the next page is obtained even though the schema references a 'nextOffset from the previous response.'

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?

Two short sentences, front-loaded with what is returned and followed by the triggering context; there is no filler. The second sentence is slightly vague in its phrasing ('when reviewing earnings') but still earns its place.

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?

This is a low-complexity read-only list tool with no required parameters and no nested objects, so little prose is needed. However, with no output schema, the pagination contract (where nextOffset and the filtered totals appear) is left unstated, which is a real gap for a paged endpoint.

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 80%, so the schema already documents limit, offset, paidSince and createdSince; the baseline is 3. The description's mention of amounts, currencies, dates and statuses loosely echoes the status/date filters but adds no filtering semantics beyond the schema.

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?

States a concrete verb-and-resource pair ('Read a page of your personal payout amounts, currencies, dates and statuses') and scopes it to the caller's own payouts, so it is clearly a personal-earnings listing. It does not, however, contrast itself with the program-oriented siblings, so the agent must infer that this is the payout view rather than a program view.

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?

'Request this when reviewing earnings' gives a situational cue but no explicit when-not condition, no mention of alternative tools, and no prerequisites. Usage is implied rather than delimited, which is the minimum viable level.

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