Skip to main content
Glama

Fda Drug Competition

Purple Book Recent Changes

purple_book_recent_changes
Read-onlyIdempotent

Return the changes section of FDA's latest monthly Purple Book report: N=newly approved, R=added in current release, U=updated. Updated or added does not necessarily mean newly licensed.

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": 50,
      "change_type": "N"
    },
    "name": "purple_book_recent_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
change_typeNo

Output Schema

NameRequiredDescriptionDefault
sourceYes
changesYes
returnedYes
dataset_noteNo
dataset_staleNo
dataset_updatedNo
dataset_age_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / dataset_age_days
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / dataset_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / dataset_stale
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / dataset_updated / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a useful semantic caveat about how to interpret change flags, but says nothing about pagination, default limit behavior, or how 'latest monthly report' is determined.

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 tight sentences, front-loaded with the core action and followed by the code legend and caveat. No filler, though the caveat sentence could be folded more compactly into the code explanation.

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?

An output schema exists, so return values need not be described, and the change-code semantics are covered. The main remaining gap is the undocumented 'query' and 'limit' parameters, which an agent would have to guess at.

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 description coverage is 0%, so the description must compensate. It does explain the change_type enum values (N=newly approved, R=added in current release, U=updated), which is real added meaning, but the 'query' and 'limit' parameters are left entirely unexplained in both schema and description.

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

Purpose4/5

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

States a specific verb and resource ('Return the changes section of FDA's latest monthly Purple Book report') and decodes the N/R/U change codes, so the agent knows exactly what data comes back. It does not explicitly differentiate itself from the sibling 'recent_changes' tool, which keeps it from a 5.

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 description implies usage (fetching the latest monthly change list) and adds an interpretive caveat that 'updated or added does not necessarily mean newly licensed.' However, it gives no explicit when-to-use vs. when-not guidance and does not point to alternatives such as the generic recent_changes or product_search tools.

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.