Skip to main content
Glama

ILIT Society - directory of allergists offering intralymphatic immunotherapy

How to get in touch

how_to_get_in_touch
Read-onlyIdempotent

Contact routes only: the Society’s email address, how a practice applies for a listing and the listing criteria, and how a person reaches a practice (a consultation or appointment request through the site, or the listing’s own phone and website). Takes no input.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation with no open-world access. The description adds useful context beyond that by specifying the exact informational scope and noting 'Takes no input'; with an output schema present, it need not explain return values.

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?

The description is a single, front-loaded sentence that immediately scopes the tool to 'Contact routes only' and then lists the included content. It is dense but efficient, with no obvious 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 zero-parameter, read-only reference tool with an output schema, the description is largely complete: it identifies the categories of contact information returned and rules out non-contact topics. The main gap is the absence of explicit guidance about when to use this instead of sibling action tools such as apply_for_listing or request_consultation.

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?

This tool has zero parameters, so the baseline is 4. The description confirms 'Takes no input,' which is consistent with the empty schema and adds a small amount of clarity beyond the structured field.

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 clearly states the tool returns contact routes and enumerates the specific content: the Society’s email, listing application/criteria information, and ways to reach a practice. It is specific and scoped with 'Contact routes only,' though it does not explicitly name or rule out the action-oriented siblings such as apply_for_listing or request_appointment.

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?

The phrase 'Contact routes only' and the content list imply this is the informational lookup tool rather than the tools that actually submit an application or appointment request. However, it gives no explicit when-to-use guidance or directs the agent to those action-oriented alternatives, leaving the routing partly to inference.

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