Skip to main content
Glama

Contacts of i22 for a topic

i22_ai_contacts_for_topic
Read-onlyIdempotent

Names the contacts of i22 for a topic with role and e-mail address. Topics: new_project, career, press, general, or the slug of a service from i22_ai_services_list. Use it when someone wants to reach i22.

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": {
      "topic": "<topic>"
    },
    "name": "i22_ai_contacts_for_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesOne of new_project, career, press, general, or the slug of a service.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the response shape (name, role, e-mail), which is useful, but says nothing about unmatched topics, empty results, or whether multiple contacts are returned per topic.

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?

Three short sentences ordered as purpose, valid inputs, then usage trigger. Nothing is padded and the constraint that selects this tool is front-loaded.

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, idempotent read tool with full schema coverage and annotations, the definition covers purpose, inputs and output fields adequately. The only small gap is behavior on invalid or unmatched topics, which the description leaves silent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter's description already lists the accepted values, so the baseline would be 3. The description earns an extra point by telling the agent where the 'slug of a service' comes from (i22_ai_services_list), which the schema does not explain.

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: it names the contacts of i22 for a topic, and adds the returned fields (role and e-mail address). An agent can tell what it gets without opening the schema. It stops short of explicitly contrasting with siblings like i22_ai_services_list, which it only cites as a source of valid slugs.

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?

Provides a clear trigger condition: 'Use it when someone wants to reach i22.' That is enough to route a contact-seeking request here. No exclusions or when-not-to-use guidance are given, which keeps it out of 5 territory.

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