Skip to main content
Glama

find_drugs_by_active_ingredient

Read-onlyIdempotent

Find Turkish drugs that share the same active ingredient or ATC code by searching with a drug name or barcode.

Instructions

Find Turkish drugs sharing the same ATC code (same active substance/class).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesDrug name or barcode; its ATC code is used to find matches.
max_resultsNoMaximum number of drugs to list.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint. Description adds that it uses the query's ATC code to find matches, which is useful but not extensive. No contradiction with annotations.

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?

Single sentence, front-loaded with key information, no unnecessary words.

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?

Given the existence of an output schema and the tool's simplicity, the description adequately covers the purpose and behavior. It doesn't explain return values but that is covered by the output schema.

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?

Schema coverage is 100% with param descriptions. The description adds value by explaining that the query can be a drug name or barcode and that the ATC code is extracted to find matches, clarifying the mechanism beyond 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?

Description clearly states the verb 'Find', resource 'Turkish drugs', and the criterion 'sharing the same ATC code (same active substance/class)'. This differentiates from siblings like search_turkish_drugs or find_drug_equivalents.

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?

Description implies usage for finding drugs by ATC code but does not explicitly state when to use this tool versus alternatives or when not to use it. No direct comparison with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/onatozmenn/klinik-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server