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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`change_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	Yes
`changes`	Yes
`returned`	Yes
`dataset_note`	No
`dataset_stale`	No
`dataset_updated`	No
`dataset_age_days`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 2, 2026
- 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"
+}
```
Changed1 schema field changedAug 6, 2026
- changedOutput schema / properties / dataset_updated / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
AddedJul 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the safety profile is already carried by annotations. The description adds value beyond that: 'latest monthly' scoping and the semantic caveat that R/U codes do not necessarily mean newly licensed, which prevents misinterpretation of results. No contradiction with 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?

Two sentences and roughly 35 words with the core action front-loaded, followed by code decoding and a domain caution. Every clause earns its place, and nothing repeats what the schema or annotations already state.

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 are covered elsewhere, annotations carry the behavioral profile, and the description handles the domain-specific codes and scoping. The only residual gap is what the query parameter searches across, which is minor given the tool's simplicity.

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 fully explains the ambiguous change_type enum (N=newly approved, R=added in current release, U=updated), which is the highest-value parameter, but says nothing about limit or query, leaving their semantics to be inferred from name and type.

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?

States a specific verb and resource: 'Return the changes section of FDA's latest monthly Purple Book report.' It also decodes the N/R/U change codes and adds the important caveat that updated/added does not necessarily mean newly licensed, which clearly differentiates it from siblings like purple_book_product_search or the generic recent_changes.

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 that this tool serves change-history queries for the latest monthly Purple Book report, so an agent can infer when to reach for it. However, it names no sibling alternatives or exclusion conditions (e.g., when to prefer purple_book_biosimilars or recent_changes), leaving differentiation to the agent.

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

All Fda Drug Competition tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.