Skip to main content
Glama

ILIT Society - directory of allergists offering intralymphatic immunotherapy

List allergens

list_allergens
Read-onlyIdempotent

List the allergens the directory tracks (name, slug, page URL) with how many listed offices treat each with ILIT. Use it to pick a valid allergen for find_practitioners or apply_for_listing, or to answer which allergens practices here treat. 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": "list_allergens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
allergensYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/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 safety is covered; the description adds value by disclosing the aggregation semantics (counts of listed offices treating each allergen with ILIT) and that no input is required. It does not discuss pagination or ordering, though with an output schema present that omission is minor.

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: what it returns, when to use it, then a clarifying 'Takes no input.' Front-loaded with the resource and zero filler.

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 no-argument, read-only listing tool with an output schema and full annotation coverage, the description supplies everything an agent needs: the payload shape, the ILIT-count semantics, and the routing to sibling tools.

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?

Zero parameters and the description correctly closes the loop with 'Takes no input,' preventing an agent from hunting for a filter argument. No further parameter meaning is possible for an input-free tool.

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?

Specific verb plus resource ('List the allergens the directory tracks'), with the returned fields (name, slug, page URL) and the ILIT office count spelled out, so an agent can distinguish it from list_practices or find_practitioners at a glance.

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?

Explicitly names the two downstream consumers ('pick a valid allergen for find_practitioners or apply_for_listing') and the standalone question it answers ('which allergens practices here treat'), giving the agent both the prerequisite role and the direct-query role.

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