Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

get_rules_version

Read-onlyIdempotent

Retrieves the rules and testing requirements for a specific Intigriti program version using its program and version IDs.

Instructions

Read the rules and testing requirements for a specific program version.

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>",
      "versionId": "<versionId>"
    },
    "name": "get_rules_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
programIdYesIntigriti program GUID from list_programs or the researcher platform.
versionIdYesVersion GUID from the current program or a matching activity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds that the payload is rules and testing requirements rather than scope data, which is modestly useful, but says nothing about size, freshness, or access restrictions on private programs.

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?

A single front-loaded sentence with no filler. It is efficient but so terse that a routing clause could have been added without hurting 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 two-parameter read-only tool with full schema coverage and rich annotations, the definition covers what is needed to invoke it. The only gap is disambiguating it from the similarly named get_scope_version.

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% and both parameters carry descriptions naming their sources (list_programs, current program, matching activity). The description only confirms the program/version pairing, so baseline 3 applies since the schema does the heavy lifting.

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 specific verb ('Read') and a concrete resource ('the rules and testing requirements') scoped to 'a specific program version'. An agent can tell this fetches rules content, though nothing explicitly separates it from the sibling get_scope_version.

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?

No when-to-use guidance, prerequisites, or named alternatives are given. The mention of 'a specific program version' implies both IDs come from a program listing, but the agent gets no rule for choosing this over get_scope_version or get_program.

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