Skip to main content
Glama

airports

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

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

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond annotations, the description discloses persistence and scoping behaviors: 'Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours' and 'scoped by your identifier'. This adds meaningful context consistent with the idempotentHint annotation.

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?

Four focused sentences, front-loaded with the core action. Each sentence adds value: purpose, when-to-use, storage format, and persistence/companion tools. No redundant information.

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?

For a simple two-parameter tool with no output schema, the description is fully complete. It covers purpose, usage, scope, persistence, and related tools, making it easy for an agent to select and invoke correctly.

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 coverage is 100% with detailed key/value descriptions, so the baseline is 3. The description adds purpose and scope context but does not introduce new parameter-specific semantics beyond what the schema already provides.

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 the tool's function with a specific verb and resource: 'Save data the agent will need to reuse later'. It distinguishes itself from siblings by explicitly mentioning 'Pair with recall to retrieve later, forget to delete'.

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?

Provides explicit when-to-use guidance: 'Use when you discover something worth carrying forward' with concrete examples. It names alternatives (recall, forget) but does not explicitly state when not to use the tool, so a near-perfect score is warranted.

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

All airports 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

A3.5/5.0
Disambiguation2/5

Many tools have distinct purposes, but the three 'ask_pipeworx' variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are highly similar and likely cause confusion. Additionally, the toolset mixes airport-specific tools with unrelated financial and research tools, creating ambiguity about when to use which.

Naming Consistency2/5

Naming conventions are inconsistent: some tools use descriptive snake_case (ai_visibility_check, ask_pipeworx), others are single verbs (remember, forget, recall), and some include brand names (pipeworx_feedback). No clear pattern emerges across the 34 tools.

Tool Count1/5

34 tools is excessive for a server named 'airports'—only 3 tools directly relate to airports (search_airports, get_airport, calculate_distance). The majority are unrelated utilities (financial, prediction markets, memory), making the scope far too broad and unfocused.

Completeness1/5

The server severely lacks completeness for its stated airport domain: there are no tools for flights, airlines, runways, or real-time data. The other included domains (e.g., financial, prediction markets) are also incomplete, with e.g., only partial coverage of company data and no update/delete operations.

Resources