Skip to main content
Glama

One service of i22 in detail

i22_ai_service_get
Read-onlyIdempotent

Returns one service of i22 with headline, intro, definition, building blocks, why i22, related case studies and the contact mailbox with people and roles. Use it once you know which service a question is about.

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": {
      "service": "<service>"
    },
    "name": "i22_ai_service_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesSlug (e.g. agentic-transformation), path or URL of a service from i22_ai_services_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile needs no restating. The description adds value beyond that by disclosing the shape of the returned record, including nested contact people and roles, which the agent otherwise could not anticipate since there is no output schema. It does not cover behavior for an unknown or ambiguous service identifier, which is the main remaining gap.

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, no filler. The content enumeration is front-loaded and every listed field earns its place by telling the agent whether this tool answers the question. The usage cue follows cleanly as the closing sentence.

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 single-parameter, read-only fetch with full annotation coverage, this is complete: the description supplies the return contents that the missing output schema would otherwise have to carry, and it tells the agent the prerequisite state of knowledge. Nothing an agent needs in order to call it correctly is absent.

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 description coverage is 100% and the single parameter already documents its accepted forms (slug such as agentic-transformation, path, or URL) and their source. The description's only added signal is the framing that the identifier corresponds to the service a question is about, which is mild. Baseline 3 applies because the schema carries the parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb-and-resource pair (returns one service of i22) and enumerates exactly what the record contains: headline, intro, definition, building blocks, why i22, related case studies, and contact mailbox with people and roles. That enumeration makes it clearly distinguishable from the sibling list tool i22_ai_services_list, which returns many services rather than one detailed record.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives real usage context: call this once you already know which service a question is about. That implicitly routes agents to look up or resolve the service first (the schema names i22_ai_services_list as the source of the slug), which is solid guidance. It stops short of an explicit when-not or a named prerequisite tool in the description itself, so it is clear but not fully prescriptive.

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