Skip to main content
Glama

Inspect an API without saving an adapter

liquid_discover
Read-onlyIdempotent

Inspect an API's structure, auth type, and endpoints by probing its URL. Use this read-only preview to understand an API before creating a reusable adapter.

Instructions

Inspect an API's shape — service name, discovery method, auth type and endpoint list — without creating or saving an adapter. Side effects: makes outbound HTTP(S) requests to url to probe it, and may call the configured LLM for APIs that publish no machine-readable spec (REST heuristic). Read-only: nothing is persisted. Use this to preview an unknown API; when you're ready to actually read data, call liquid_connect, which discovers and maps and saves a reusable adapter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesBase URL of the API to inspect (same forms as liquid_connect's url).
credentialsNoOptional secrets for an auth-walled API, e.g. {"api_key": "..."}, {"token": "..."}, or {"username": "...", "password": "..."}. Stored encrypted under ~/.liquid and applied automatically on every later fetch. Omit for public APIs.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceNo
discovery_methodNoHow it was found: openapi, graphql, soap, grpc, websocket, mcp, rest_heuristic, or browser.
auth_typeNo
endpointsNo
errorNo
Behavior5/5

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

Discloses side effects: makes outbound HTTP(S) requests and may call LLM for REST heuristic. States read-only and nothing persisted. No contradiction with annotations (readOnlyHint, destructiveHint, idempotentHint).

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?

Description is about 5 well-structured sentences, no fluff, front-loaded with key action. Every sentence adds value.

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?

Given output schema exists, description adequately covers the return shape (service name, discovery method, auth type, endpoint list). No gaps.

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

Parameters4/5

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

Schema coverage is 100%, description adds meaning by explaining credentials are optional, stored encrypted, and implies automatic usage on later fetches. Adds value beyond schema.

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 it inspects an API's shape (service name, discovery method, auth type, endpoint list) without saving, and distinguishes from liquid_connect which also saves an adapter.

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?

Explicitly says to use for previewing unknown APIs, and to call liquid_connect when ready to read data. Provides clear when-to-use and when-not-to-use guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ertad-family/liquid'

If you have feedback or need assistance with the MCP directory API, please join our Discord server