Skip to main content
Glama
Sign In

Openremedies

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Substance Uses

get_substance_uses
Read-onlyIdempotent

Approvals by jurisdiction (verbatim + normalized status), verbatim indications, and evidence assertions for a substance and its labeled salt/form family. Sourced from OpenRemedies, which draws on national and regional medicines registers; call get_coverage for the current list of registers and jurisdictions.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 2,
      "substance_id": 10059
    },
    "name": "get_substance_uses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
jurisdictionNoJurisdiction filter, e.g. US or EU
substance_idYesSubstance id from resolve_substance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds useful behavioral context beyond annotations: it names the source (OpenRemedies), clarifies that it covers a substance plus its labeled salt/form family, and indicates the data types returned. It does not cover pagination behavior or rate limits, but with annotations covering safety this is a solid addition.

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?

Two sentences efficiently front-load the data categories, then add source context and a pointer to get_coverage. Every sentence contributes relevant information with no waste.

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 output schema and four parameters, the description does a good job enumerating the return categories and source. It does not explain pagination (limit/offset) or output structure in detail, but given the annotations and parameter schema, it is nearly complete for an agent to call the tool correctly.

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 coverage is 50%. The description adds meaning for substance_id by mentioning the salt/form family scope, and 'by jurisdiction' aligns with the jurisdiction filter. However, the limit and offset parameters are undocumented in both schema and description, leaving a clear gap.

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 the specific data returned: approvals by jurisdiction, verbatim indications, and evidence assertions for a substance and its salt/form family. It clearly distinguishes the scope and points to get_coverage for register coverage, making it easy to tell this tool apart from generic evidence retrieval.

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?

The description gives clear context for use by explaining the data source and directing the agent to get_coverage for current registers and jurisdictions. It implies the tool is for substance-level approvals and indications, but does not explicitly state when not to use it or name a specific alternative like get_evidence.

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

All Openremedies toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources