Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

list_program_activity

Read-onlyIdempotent

Read paginated activity for a specific Intigriti program, filter by createdSince or follow status, and use nextOffset to continue tracking updates.

Instructions

Read activity for one program. Intigriti paginates the account-wide feed first. Pass nextOffset to keep reading and createdSince to narrow the time window.

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": {
      "programId": "<programId>"
    },
    "name": "list_program_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoSource records per request, before local filtering.
offsetNoUse nextOffset from the previous response.
followingNoFilter by whether you follow the program.
programIdYesIntigriti program GUID from list_programs or the researcher platform.
createdSinceNoUnix timestamp in seconds (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered; the description instead contributes the genuinely non-obvious behavior that Intigriti paginates the account-wide feed and filters locally, which changes how paging and limits behave. It omits what happens when the filtered result is smaller than limit or how termination is detected, keeping it below 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?

Three short sentences, front-loaded with purpose before pagination detail, with essentially no filler. The middle sentence about account-wide pagination is compressed to the point of slight ambiguity, which costs it a point but not readability.

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 five-parameter paginated read tool with full schema coverage and declarative annotations but no output schema, the description covers the one thing structured fields cannot: the account-wide-then-filter pagination model. Minor gaps remain around the nextOffset-versus-offset handoff and end-of-feed detection, but nothing critical is missing for a correct call.

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 100%, so the baseline is 3. The description adds intent for two parameters (nextOffset for continuation, createdSince for narrowing) but does not resolve the naming mismatch — the parameter is 'offset' while the text says 'nextOffset' — nor does it explain limit or following beyond what the schema already documents.

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?

"Read activity for one program" gives a specific verb (read) and resource (activity) plus an explicit scope (one program), which separates it from account-wide or unrelated siblings like get_program and list_payouts. It stops short of naming an alternative, so sibling differentiation is inferred from the resource rather than stated.

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?

The description tells the agent how to continue reading (pass nextOffset) and how to narrow results (createdSince), which is useful implied usage for a paginated feed. It never states when this tool should be chosen over another, nor any exclusions or preconditions such as needing a programId from list_programs — that only appears in the schema.

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