Skip to main content
Glama
Sign In

A2A Peptides

by io.github.Dosidal
OverviewDiscussionsAdmin

Get Lot Coa

get_lot_coa
Read-onlyIdempotent

Certificate of analysis for a lawful lot of a presentation, where the pathway permits (decision_id required).

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": {
      "presentation_id": "<presentation_id>",
      "lot": "<lot>",
      "decision_id": "<decision_id>"
    },
    "name": "get_lot_coa"
  }
}

Input Schema

NameRequiredDescriptionDefault
lotYes
decision_idYes
presentation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond noting that decision_id is required (already in the schema). It does not mention error cases, permission requirements, or what happens if the pathway does not permit the request.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, short sentence with no wasted words. However, it is under-specified to the point of being cryptic, so the brevity does not serve the agent's comprehension. It is concise but not effectively structured to convey essential context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (which reduces the need to explain returns), the description fails to define critical terms like 'lawful lot' and 'pathway', and does not address how the three required parameters interact. An agent cannot reliably determine correct usage without additional context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so the description carries the full burden of explaining parameters. It only mentions decision_id as required, without explaining its purpose, format, or relationship to the pathway. It offers no meaning for lot or presentation_id, leaving the agent without enough information to construct valid calls.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (certificate of analysis) and scope (a lawful lot of a presentation), which goes beyond a tautology. However, terms like 'lawful lot' and 'presentation' are unexplained and the description does not distinguish this tool from siblings such as get_safety_label or get_label_and_indication, leaving ambiguity about its exact role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The phrase 'where the pathway permits' hints at a condition but does not clarify how to determine that condition or when to choose another tool. There are no explicit exclusions or alternative recommendations.

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