Skip to main content
Glama

IRM Consulting & Advisory

Get one IRM service

get_service
Read-onlyIdempotent

Full details of one IRM service or program: summary, audience, frameworks covered, published starting price, page URL, booking link and the related free self-assessment tool.

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": {
      "id": "<id>"
    },
    "name": "get_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesService id from list_services (equal to the page slug).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 safety is covered. The description adds genuine value by disclosing the shape of the returned payload (summary, audience, frameworks, price, URL, booking link, related self-assessment) — important since no output schema exists.

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?

One front-loaded sentence that puts the resource first and the field inventory second. The colon-separated field list is dense but every item carries information; no filler or repetition.

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 single-id lookup with no output schema, the description compensates well by describing the return contents and referencing the related free self-assessment tool. The only missing piece is explicit routing to list_services for id discovery, which lives in the schema rather than the description.

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 single parameter is a fully enumerated id with a description tying it to list_services and the page slug. The description adds no further meaning about the id, 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?

The description gives a specific verb-and-resource ('Full details of one IRM service or program') and enumerates the fields returned (summary, audience, frameworks, price, URL, booking link, self-assessment). This is clearly distinguishable from a list operation, though it never names list_services as the companion tool inside the description itself.

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: an agent can infer this is for fetching details on a single known service. There is no explicit statement of when to use it versus siblings (get_pricing, check_availability) or any prerequisite such as obtaining the id first, so the guidance is adequate but thin.

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