Skip to main content
Glama

ILIT Society - directory of allergists offering intralymphatic immunotherapy

Apply for a listing

apply_for_listing

For an allergist or immunologist offering ILIT: submit a listing application. The Society checks board certification against the ABAI register and creates the listing by hand; nothing is published automatically. Requires confirm_accurate=true and confirm_terms=true.

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": {
      "practice_name": "<practice_name>",
      "phone": "<phone>",
      "contact_email": "<contact_email>",
      "practitioner_first_name": "<practitioner_first_name>",
      "practitioner_last_name": "<practitioner_last_name>",
      "credentials": "<credentials>",
      "accepting_new_patients": "<accepting_new_patients>",
      "offices": "<offices>",
      "confirm_accurate": "<confirm_accurate>",
      "confirm_terms": "<confirm_terms>"
    },
    "name": "apply_for_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
bioNoShort bio, up to 1200 characters.
phoneYesPractice phone.
accessNo
officesYesOne or more offices.
parkingNo
intervalNoe.g. "4 weeks".
allergensNoAllergen names or slugs from list_allergens.
languagesNo
agent_nameNoOptional: the assistant sending this.
injectionsNoe.g. "3".
credentialsYes
minimum_ageNo
website_urlNoPractice website.
confirm_termsYesMust be true: the applicant agrees to the listing criteria.
contact_emailYesWhere the Society replies (not shown on the site).
cost_includesNo
practice_nameYesClinic name.
injection_siteNo
insurance_noteNo
waitlist_weeksNo
allergen_detailNoExtracts per allergen, one per line.
ilit_since_yearNo
selfpay_low_usdNo
treats_childrenNo
confirm_accurateYesMust be true: the details are accurate and the applicant is a board-certified allergist or immunologist offering ILIT.
selfpay_high_usdNo
ultrasound_guidedNo
appointment_minutesNo
observation_minutesNo
video_first_consultNo
board_certified_abaiNoBoard certified by the American Board of Allergy and Immunology.
other_certificationsNo
accepting_new_patientsYes
practitioner_last_nameYes
practitioner_first_nameYes
required_before_startingNo

Output Schema

NameRequiredDescriptionDefault
okYes
errorsNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true; the description adds real value beyond them by disclosing that the Society verifies ABAI board certification and posts listings manually, so nothing is published automatically. That is the key behavioral fact an agent needs to set expectations. It stops short of saying what a resubmission does, despite idempotentHint=false.

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, front-loaded with eligibility, then process behavior, then hard requirements. No filler and no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 36-parameter application tool the description covers eligibility, manual review, and the two confirmation gates, and the output schema relieves it of explaining return values. It does not help the agent decide how to populate the large optional field set or reference list_allergens for allergen values, so it is adequate rather than complete.

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

Parameters2/5

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

The schema has 36 parameters at only 39% description coverage, so the description needs to compensate and largely does not. It explains only the two confirm_* flags, leaving most fields (allergens sourcing, ilit_since_year, ultrasound_guided, interval, waiting-list fields, office sub-object) undocumented in prose. That is a clear shortfall against the low coverage baseline.

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 names a specific verb (submit), a specific resource (listing application), and the exact audience/qualifier ('an allergist or immunologist offering ILIT'). That qualifier alone separates it from siblings like request_appointment or find_practitioners, so an agent can route correctly without opening a schema.

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?

It states clearly when this tool applies (the caller is an ILIT-offering allergist/immunologist applying to be listed) and hard preconditions (confirm_accurate=true, confirm_terms=true). It does not name alternatives or say when not to use it, e.g. that practitioners already listed should not re-apply.

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