Skip to main content
Glama

ReefAPI

by io.github.reefapi

get_engine_schema

Read-onlyIdempotent

COMPACT overview of ONE engine: every action with its description, required params and what it returns — but NOT the full param detail (kept lean so a 90-action engine stays token-cheap). Call this after search_engines to pick the right ACTION, then get_action_schema(engine, action) for that action's full params before call_engine.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineYesThe engine's name (the `engine`/`name` field from search_engines or get_catalog, e.g. 'zillow', 'amazon'). Returns each action with its description, required params, and what it returns.

Schema Changelog

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

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and open world; the description adds that the tool returns a lean overview to save tokens, setting accurate expectations beyond the 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: first defines the tool's purpose, second provides workflow context. No waste, front-loaded with key 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?

With one parameter fully described, annotations covering safety, and output behavior explained, the description is complete for the tool's simplicity and fits its role in the workflow.

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% and the schema description already states what the parameter is and what the tool returns; the tool description doesn't add new parameter-level meaning beyond the 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?

Explicitly states it provides a compact overview of one engine's actions, descriptions, required params, and returns, and distinguishes from similar tools by naming the workflow sequence.

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?

Clearly states it should be called after search_engines and before get_action_schema, establishing a clear usage order and specifying when to use alternatives.

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

All ReefAPI 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.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: search_engines for keyword-based discovery, get_catalog for a full list, get_engine_schema for action overview, get_action_schema for detailed parameters, and call_engine for execution. No overlap.

Naming Consistency5/5

Consistent snake_case with verb_noun pattern: search_*, get_catalog, get_*schema, call_engine. All follow a predictable structure.

Tool Count5/5

5 tools is well-scoped for an API discovery and invocation workflow. It covers search, exploration, and execution without being excessive or insufficient.

Completeness5/5

The tool surface covers the full lifecycle: engine discovery (search_engines, get_catalog), action schema (get_engine_schema, get_action_schema), and execution (call_engine). No obvious gaps.

Resources