Skip to main content
Glama

IRM Consulting & Advisory

List IRM services

list_services
Read-onlyIdempotent

List the services and programs IRM Consulting & Advisory offers (vCISO, AI governance, GRC, SOC 2, ISO 27001, ISO 42001, CMMC, CPCSC, penetration testing and more), each with a one-line summary, starting price and page URL. Optionally filter by kind or by a framework name.

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

Input Schema

NameRequiredDescriptionDefault
kindNoservice: core services. program: focused compliance engagements delivered through the vCISO tiers.
frameworkNoOnly services covering this framework, e.g. "SOC 2", "ISO 42001", "CMMC", "NIST AI RMF".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 closed-world, so the safety profile is handled. The description adds real value by disclosing the shape of each returned entry — one-line summary, starting price and page URL — plus the fact that filtering is optional rather than required.

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, front-loaded with what the tool returns, then the optional filters. No filler, and the listing of offerings doubles as scope documentation rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with full schema coverage and annotations, the description closes the remaining gap by describing the returned fields in the absence of an output schema. Nothing an agent needs in order to call it correctly 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%, and the enum and framework parameter already carry descriptions in the schema. The description only restates that filtering is optional, adding no syntax, matching behavior, or format detail beyond what the schema provides, so the baseline 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?

The description uses a specific verb+resource ("List the services and programs IRM Consulting & Advisory offers") and enumerates the covered offerings, so the scope is unambiguous. It does not explicitly differentiate itself from siblings like get_service or list_free_products, which keeps it from 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?

It states that filtering by kind or framework is optional, which implies the default call returns everything, but it never says when to prefer this over get_service or list_free_products. Usage is inferable rather than guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources