Skip to main content
Glama

ILIT Society - directory of allergists offering intralymphatic immunotherapy

Search the Journal

search_journal
Read-onlyIdempotent

Search the Society’s Journal, longer articles for patients and practitioners, by keywords and/or topic. Returns matching articles with title, date, summary, key points and URL; read one in full with get_article. For a short factual answer use answer_question instead.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many articles to return (default 5, max 20).
queryNoKeywords to match in titles and text, e.g. "grass pollen trial".
topicNoOptional topic: For patients, Evidence, Cost, For practitioners or Society news.

Output Schema

NameRequiredDescriptionDefault
articlesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Default 5."New value: +"How many articles to return (default 5, max 20)."
    • changedInput schema / properties / query / description
      Previous value: -"Keywords."New value: +"Keywords to match in titles and text, e.g. \"grass pollen trial\"."
    • changedInput schema / properties / topic / description
      Previous value: -"For patients, Evidence, Cost, For practitioners, Society news."New value: +"Optional topic: For patients, Evidence, Cost, For practitioners or Society news."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered; the description adds useful context that results are longer patient/practitioner articles and enumerates what comes back (title, date, summary, key points, URL). It stops short of describing result ranking or relevance ordering, which would have made it 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each earning its place: what it searches, what it returns and how to read fully, then the alternative for short answers. The core purpose is front-loaded with no 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?

Complete for a read-only search tool: scope, inputs, result shape and the handoff for full reads and short answers are all covered, and an output schema exists so return details need not be elaborated further.

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

Parameters3/5

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

Schema description coverage is 100%, with the query example, the topic enum values and the limit default/max all documented in the schema. The description adds only that keywords and topic can be combined ("and/or"), so it sits at the baseline for a fully-documented schema.

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 specific verb and resource ("Search the Society's Journal, longer articles for patients and practitioners") plus the dimensions it searches on (keywords and/or topic). It also distinguishes itself from both siblings by noting full reads go to get_article and short factual answers go to answer_question.

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 routes the agent: use get_article to read one in full, and use answer_question for a short factual answer. Both the when-to-use and the when-to-use-something-else conditions are stated rather than inferred.

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