Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

list_programs

Read-onlyIdempotent

Browse Intigriti program cards with bounty ranges and links, filtering by type, status, or following. Use nextOffset to page through results, including pages with no visible programs.

Instructions

Browse a page of program cards, including bounty ranges and Intigriti links. Use nextOffset to continue even when a page contains no visible programs.

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

Input Schema

NameRequiredDescriptionDefault
limitNoSource records per request, before local filtering.
offsetNoUse nextOffset from the previous response.
typeIdNoProgram type, e.g. 1 for bug bounty or 2 for hybrid.
statusIdNoProgram status, e.g. 3 for open, 4 for suspended, 5 for closing.
followingNoFilter by whether you follow the program.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds a genuinely non-obvious behavioral trait beyond the annotations: results are locally filtered, so a page can be visually empty yet still warrant continued pagination. It stops short of describing ordering, total counts, or the response envelope.

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

Conciseness5/5

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

Two sentences, both load-bearing: the first establishes scope and payload, the second front-loads the pagination caveat that would otherwise cause an agent to stop early. No filler, redundant phrasing, or restated metadata.

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?

With zero required parameters, full schema coverage, rich annotations, and no output schema, the description supplies what matters most for correct invocation: the page-and-continue pagination model and the local-filtering caveat. It could go one step further by clarifying what 'Intigriti links' are or how filtering interacts with page size, but nothing essential to calling it is missing.

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 coverage is 100%, so all five parameters including limit, offset, typeId, statusId, and following are already documented. The description mentions nextOffset but adds no syntax or semantics beyond what the schema states, and notably the schema's own offset field is the one that refers to nextOffset, a naming mismatch the description does not resolve. Baseline 3 applies when the schema carries the parameter burden.

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?

Names a specific verb and resource ('Browse a page of program cards') and adds what the cards contain ('bounty ranges and Intigriti links'), which is more than a restatement of the name. It does not explicitly contrast itself with siblings like get_program or list_program_activity, so an agent must infer that this is the list-level entry point.

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?

Provides a concrete usage rule for pagination: keep calling with nextOffset even when a page looks empty, which is actionable guidance. It gives no indication of when to pick this tool over get_program for a single program or over list_program_activity, so alternative selection is left implicit.

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