Skip to main content
Glama

List & Search Eye Conditions Library

list_eye_conditions
Read-onlyIdempotent

Searches or filters ArkSight's library of 26 eye conditions (Refractive, Cornea/Lens, Retina/Macula/Vitreous, Optic Nerve/Neurological), returning plain-English explanations, pronunciation guides, hallmark visual symptoms, and direct interactive simulation links.

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_eye_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoOptional search keyword (e.g. 'macula', 'halos', 'curtain', 'near', 'glaucoma').
categoryNoOptional anatomical category filter.

Output Schema

NameRequiredDescriptionDefault
countYes
conditionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / conditions / items / properties / conditionPageUrl
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / conditions / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "pronunciation",
      -  "category",
      -  "urgent",
      -  "urgentNote",
      -  "summary",
      -  "symptoms",
      -  "simulateUrl"
      -]New value: +[
      +  "id",
      +  "name",
      +  "pronunciation",
      +  "category",
      +  "urgent",
      +  "urgentNote",
      +  "summary",
      +  "symptoms",
      +  "conditionPageUrl",
      +  "simulateUrl"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the corpus size (26 conditions), the taxonomy covered, and the shape of each result (plain-English explanation, pronunciation guide, hallmark symptoms, simulation links). Only result-volume or pagination behavior is left unstated.

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?

A single front-loaded sentence with no filler; the verb and scope come first and the return contents follow. It is a long run-on sentence, but every clause carries information an agent would otherwise have to infer.

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 two-optional-parameter read tool with a full output schema and complete annotations, the description covers purpose, scope, and return contents adequately. The one remaining gap is routing guidance versus the sibling tools, which the description does not address.

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%, so both parameters are already documented and the baseline is 3. The description's category list (Refractive, Cornea/Lens, Retina/Macula/Vitreous, Optic Nerve/Neurological) roughly conveys the taxonomy but does not map onto the actual enum values (all/refractive/anterior/retinal/neuro), so it adds flavor rather than precise parameter meaning.

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?

States a specific verb pair ("searches or filters") plus the exact resource ("ArkSight's library of 26 eye conditions") and enumerates the subject categories covered. The scope is unambiguous, though it never names a sibling tool to distinguish itself from get_eye_care_resources or assess_visual_symptoms.

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?

Usage is only implied: the tool searches or filters a condition library, and both parameters are optional so a bare call appears to list everything. There is no explicit statement of when to prefer this over assess_visual_symptoms (symptom triage) or simulate_vision (simulation), and no exclusion guidance.

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.