Skip to main content
Glama

The HHS 503A peptide conditions

hhs_conditions
Read-onlyIdempotent

Returns the conditions in HHS's 503A peptide enforcement discretion policy, quoted word for word, with the policy's link and the peptides it lists in Appendix A. Does not count as a lookup.

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": "hhs_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: the content is verbatim quoted, includes an external policy link, and enumerates Appendix A peptides, plus a hint about non-lookup accounting behavior. It stops short of saying whether the text is static/cached or what the response shape is.

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

Conciseness4/5

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

Two tightly packed sentences with the scope front-loaded and no filler. The only flaw is the final sentence, whose brevity comes at the cost of clarity about what 'count as a lookup' means.

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, the description carries the burden of describing return values, and it does so (verbatim conditions, policy link, Appendix A peptide list). For a zero-parameter, closed-world content tool this is nearly sufficient; only the exact response format/packaging is left unstated.

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 nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description correctly implies a fixed, unparameterized payload rather than suggesting any configuration.

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 a specific verb ('Returns') and a specific resource ('the conditions in HHS's 503A peptide enforcement discretion policy'), then enumerates the payload (verbatim text, policy link, Appendix A peptides). An agent knows exactly what this yields without opening the schema.

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?

The closing line 'Does not count as a lookup' implies a contrast with the lookup-family siblings (e.g. lookup_rules), giving an indirect routing hint. However, it never states when an agent should call this instead of those tools, and the phrase is cryptic enough that it could be read as a quota statement rather than a tool-selection cue.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources