Skip to main content
Glama
Sign In
amr-mcp

amr-mcp

by pabloestepaa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_drug_classes

Read-only

List all drug classes in the antimicrobial resistance gene catalog, including the number of entries for each class.

Instructions

All drug classes in the catalog with the number of entries for each.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that entries are counted per class, but that is return-value information already captured by the existing output schema, and it says nothing about ordering, size, or whether results are cached or complete.

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?

A single short sentence with no filler; the resource is front-loaded and the returned attribute follows immediately. Nothing could be removed without losing information.

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?

With no parameters, an output schema, and annotations covering the safety profile, very little is required of the description. It is nearly complete, missing only a note about scale or ordering of the class list and any relationship to the sibling catalog_info tool.

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 there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies the call is unfiltered and catalog-wide, which is the only parameter-adjacent fact worth conveying.

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?

The description names a specific resource (drug classes) and states exactly what accompanies each one (the number of entries), so an agent knows this is a catalog enumeration rather than a search. It does not distinguish itself from siblings such as catalog_info, which could plausibly overlap, but the resource noun makes the distinction mostly self-evident.

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?

There is no explicit when-to-use or when-not-to-use statement, and no alternative tool is named. Usage is only implied: an agent can infer this is the tool for browsing drug classes when it wants a taxonomy overview, but nothing tells it whether to prefer catalog_info or a search tool first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools