Skip to main content
Glama
Intigriti Researcher MCP

Intigriti Researcher MCP

by bunny0417

get_program

Read-onlyIdempotent

Fetch one program's current rules, version IDs, scope counts by type and tier, and platform link by program ID.

Instructions

Read one program's current rules, version IDs, scope counts by type and tier, and platform link.

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

Input Schema

NameRequiredDescriptionDefault
programIdYesIntigriti program GUID from list_programs or the researcher platform.

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, non-destructive, open-world, so the safety profile is covered. The description still earns credit by disclosing the returned content (current rules, version IDs, per-type/per-tier scope counts, platform link), which matters because there is no output schema. It does not say whether rules are inlined in full or summarized, which is the remaining behavioral unknown.

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?

A single front-loaded sentence with the verb first and the payload enumerated after it. No filler, no repetition, nothing to trim.

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 one-parameter read tool with full annotation coverage, the description covers what is returned and what identifies the target. Without an output schema, the return-value enumeration does the necessary work. The missing piece is routing guidance against the sibling version/scope getters.

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% — programId is documented as a UUID GUID sourced from list_programs or the researcher platform. The description adds only the phrase "one program's," which merely restates that the parameter selects a single program. Baseline 3 is correct when 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?

Specific verb+resource: "Read one program's current rules, version IDs, scope counts by type and tier, and platform link." The phrase "one program's" implicitly contrasts with list_programs, and the enumerated payload makes the tool's identity clear. It stops short of naming a sibling explicitly, so not a 5.

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?

Usage is only implied — you call this when you already have a programId and need that program's detail. There is no statement of when to prefer get_rules_version or get_scope_version, nor any exclusion or prerequisite guidance. Adequate but with a clear gap.

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