Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

get_scope_version

Read-onlyIdempotent

Read scope counts by type and tier for a program version, and compare two versions to see how the inventory changed.

Instructions

Read scope counts by type and tier for one version. Use two versions to compare how inventory changed.

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_scope_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

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that the result is broken down by type and tier, but says nothing about pagination, result size, or what an empty/invalid version returns.

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 short sentences, zero filler, with the core operation front-loaded and the comparative usage hint following. Every sentence earns its place.

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 simple two-parameter read tool with full schema coverage, annotations, and no output schema, the description covers what is read and the shape of the result (counts by type and tier). It is slightly thin on edge cases but nothing essential for a correct call 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%: both UUID parameters are documented in the schema, including where to obtain each GUID. The description reinforces the one-version scoping but adds no format or validation meaning beyond what the schema already provides, so the baseline of 3 applies.

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 and resource: 'Read scope counts by type and tier for one version.' The 'for one version' scoping and the breakdown dimensions give an agent a concrete picture of the operation, though it never names how it differs from siblings like get_rules_version or get_program.

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?

'Use two versions to compare how inventory changed' gives one actionable usage pattern (call twice, diff the results). However, there is no explicit when-not guidance, no statement of prerequisites, and no routing away from related siblings, so the guidance is implied rather than complete.

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