Skip to main content
Glama

Deepsky Aviation Regulations

by com.deepskyai

Get Regulation Unit

get_regulation_unit

Fetch one complete regulatory unit (a clause, section or table) by its identifier, with heading path, page numbers, jurisdiction and source URL. Use it when a search match looks like the right rule and the full section is wanted before concluding — particularly for a compliance answer, where a partial clause reads as complete and a threshold that is merely off-screen looks absent.

The identifier to pass is the document_id field of a search match. Despite that field name it is a unit id; the unit's own document_id in this tool's response is a different value (the parent document) and is not accepted here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
unit_idYesThe `document_id` value from a search match — a UUID identifying one regulatory unit.

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description must carry full burden. It explains input vs output document_id confusion, but does not disclose rate limits, authentication needs, or side effects. Adequate but not comprehensive.

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?

Well-structured with clear sentences. The second paragraph is slightly verbose but adds crucial detail. Could be slightly more concise, but overall efficient.

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?

For a simple one-parameter tool with no output schema, the description provides sufficient context: what it returns, where the input comes from, and use cases. Lacks explicit return format but acceptable given simplicity.

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

Parameters5/5

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

Adds significant value beyond schema: clarifies unit_id is the document_id from search match, explains naming confusion (unit id vs parent document_id), and sets expectations. Schema coverage is 100% but description enhances usability.

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?

Clearly states it fetches one complete regulatory unit, listing return fields (heading path, page numbers, jurisdiction, source URL). Distinguishes from sibling tool 'search_aviation_regulations' by specifying it retrieves full units after a search.

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?

Explicitly says to use when a search match looks like the right rule and full section is wanted, particularly for compliance answers. Implicitly says not to use for initial search. Could add explicit when-not-to-use, but guidance is sufficient.

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

All Deepsky Aviation Regulations toolsInspect
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.

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have clearly distinct roles: one searches for regulatory text, the other fetches a specific unit by ID. There is no overlap or ambiguity, as each serves a separate step in the lookup workflow.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern (search_aviation_regulations, get_regulation_unit) with lowercase and underscores. The verbs 'search' and 'get' are both action-oriented and align with their functions.

Tool Count3/5

Two tools feels thin for a regulatory information server, but it covers the core search-and-fetch workflow. The count is borderline appropriate for a tightly scoped read-only lookup service, though additional tools like listing jurisdictions or browsing tables could enhance it.

Completeness4/5

The server covers the essential lifecycle of regulatory lookup: search returns relevant matches, and get retrieves the complete unit. Minor gaps exist (no ability to browse the corpus or list all available parts), but these are not critical for answering compliance questions.

Resources