Skip to main content
Glama
Sign In

A2A Peptides

by io.github.Dosidal
OverviewDiscussionsAdmin

Search Cleared Items

search_cleared_items
Read-onlyIdempotent

Presentations that passed the gate for a jurisdiction, pathway and actor class (a query by substance, brand or holder; optional banner filter on the shelf of record). Only cleared statuses are returned; every item carries its availability block (banners, pos_count, product_urls).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "jurisdiction": "<jurisdiction>"
    },
    "name": "search_cleared_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
bannerNo
pathwayNolicensed_medicine
actor_classNowholesale_distributor
decision_idNo
jurisdictionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds useful behavioral detail beyond annotations: only cleared statuses are returned, and each result includes an availability block with banners, pos_count, and product_urls. There is no contradiction with the 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?

The description is compact and front-loaded with the core purpose. Every sentence adds meaningful information without padding or redundancy, making it easy for an agent to parse quickly.

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 7-parameter tool, the description covers the main search semantics and return behavior, and an output schema is present. The main gap is the unexplained decision_id parameter and the limit parameter, though both are optional and do not block correct basic usage.

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 description coverage is 0%, so the description must compensate. It effectively explains the query parameter (substance, brand, or holder), the optional banner filter, and the scoping role of jurisdiction, pathway, and actor_class. However, limit and decision_id are not described, so coverage is incomplete.

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 clearly identifies the operation: searching for presentations that passed the gate, scoped by jurisdiction, pathway, and actor class. It also specifies the query dimensions (substance, brand, or holder) and distinguishes this from a general availability search by emphasizing cleared statuses only.

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 contextual guidance on when this tool is appropriate: when you need cleared presentations for a jurisdiction and want availability data. It does not explicitly name sibling alternatives or exclusions, but the scope is concrete enough that an agent can infer when to select it.

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

All A2A Peptides 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