Skip to main content
Glama

ILIT Society - directory of allergists offering intralymphatic immunotherapy

About ILIT Society

get_facts
Read-onlyIdempotent

Overview of the site in one call: what ILIT Society is, live counts (offices, practitioners, states, allergens, articles), how finding a practitioner and sending requests work, its limits, the contact address and links to its machine-readable docs. Use it for context about the site itself; for a question about ILIT use answer_question, for contact routes only use how_to_get_in_touch. 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": "get_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 meaningful behavior beyond that: it is a single-call aggregation returning live counts, it surfaces site limits, and it exposes links to machine-readable docs. It does not discuss staleness or cost of the live counts, which keeps it from a 5.

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?

Front-loaded with the core statement, and the routing exclusions come last where they belong. The single long enumeration sentence is dense but every item earns its place; light trimming would improve scanability.

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?

An output schema exists, so return-shape explanation is not required, and the description still tells the agent what families of data come back (counts, workflow explanation, limits, contact, docs). For a zero-parameter overview tool this is as complete as needed.

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?

The tool takes zero parameters, so the schema baseline is 4. The description confirms "Takes no input," which is consistent and removes any doubt about required arguments.

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?

States a concrete resource and scope: an overview of the site in one call, enumerating exactly what it covers (what ILIT Society is, live counts, how finding a practitioner and sending requests work, limits, contact address, doc links). It is immediately distinguishable from siblings like answer_question and how_to_get_in_touch.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ("for context about the site itself") and explicit alternatives with their selecting conditions: answer_question for ILIT questions, how_to_get_in_touch for contact routes only. The agent does not have to infer routing.

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