get_compliance_status
Read-onlyIdempotent
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| media_buy_id | Yes | Media buy UUID to check |
discovery
by dev.nexbid
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable behavioral detail by enumerating the specific checks performed: no cookies, no fingerprinting, contextual targeting, data residency, revenue transparency, consent basis, and agent transparency. It also describes the output format, giving a fuller behavioral picture.
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 well-organized into distinct sections (tool_description, when_to_use, combination_hints, output_format), each concise and purposeful. No filler or redundant content, and the key information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With only one parameter, clear annotations, a defined output format, and explicit workflow hints, the description fully covers what an agent needs to select and invoke this tool correctly. The combination hints also situate it within the broader campaign lifecycle.
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?
The sole parameter media_buy_id is already fully described in the schema with 'Media buy UUID to check' and 100% schema coverage. The description does not add further parameter-level detail beyond referencing 'a media buy' context, so the schema carries the semantic burden.
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 states 'Check nDSG/GDPR/EU AI Act compliance status for a media buy' with a specific verb and resource, and it uniquely distinguishes this tool from sibling tools like get_campaign_report or get_inventory_item. The compliance scope is explicit and actionable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'when_to_use' section explicitly states 'Before activating a campaign or for compliance audits,' and the combination hint 'create_media_buy → get_compliance_status → activate' provides concrete workflow guidance. This clearly communicates when to use this tool versus alternatives.
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.
TDQS
A4.4/5.0
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between get_product and nexbid_product, which are explicitly described as aliases, and between list_products and nexbid_search with content_type='product'. This could cause confusion, though descriptions help clarify. Other tools like activate, pause, and cancel are well-differentiated for media buy lifecycle management.
Naming Consistency3/5
The naming is mixed with no consistent pattern. Some tools use verb_noun (e.g., create_media_buy, list_inventory), others use noun_verb (e.g., nexbid_search, nexbid_purchase), and some are single verbs (e.g., activate, pause, cancel). While readable, the lack of a uniform convention across the set reduces predictability.
Tool Count4/5
With 19 tools, the count is on the higher side but reasonable for the dual domains of media buying and marketplace discovery. It covers operations like listing, creating, managing, and reporting, which justifies the number. However, it borders on feeling heavy, especially with overlapping tools like get_product and nexbid_product.
Completeness5/5
The tool set provides comprehensive coverage for both media buying (create, submit, activate, pause, cancel, track, settle, report, compliance) and marketplace discovery (search, categories, product details, purchase, order status). There are no obvious gaps; workflows are well-supported with clear combination hints, ensuring agents can handle end-to-end tasks without dead ends.