Skip to main content
Glama

ReefAPI

by io.github.reefapi

call_engine

Call a ReefAPI engine action — POST //v1/ with params. Returns the uniform { ok, data, meta, error } envelope. Get param names from get_engine_schema first. Needs YOUR ReefAPI key (the local server reads REEFAPI_KEY; the hosted server reads the Authorization: Bearer ak_live_... header you configure on the connection). Get a key at https://reefapi.com. Failed calls cost no credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe action to run on that engine (e.g. 'search'), as listed by get_engine_schema.
engineYesThe engine's name to call (e.g. 'zillow'), as returned by search_engines or get_catalog.
paramsNoThe action's parameters as a JSON object, e.g. {'query': 'NYC'}. Get the valid param names and values from get_action_schema first. Omit or pass null for actions that take none.

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 readOnlyHint=false and openWorldHint=true. The description adds valuable behavioral details: the return envelope structure ({ ok, data, meta, error }), authentication requirements (ReefAPI key, local vs hosted), and credit policy. It does not contradict annotations and provides transparency beyond structured data.

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 concise with four sentences, each adding critical information: the core action, return format, prerequisite, authentication, and cost. It is front-loaded with the main purpose. No redundant or extraneous content.

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 tool with no output schema and open-world behavior, the description covers essential contextual aspects: the return envelope shape, authentication setup, credit usage, and the need to consult schema tools. It is sufficiently complete for an agent to use the tool correctly.

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% with descriptions for all three parameters. The description adds context by directing users to get_engine_schema for parameter names and get_action_schema for valid values, which complements the schema. This extra guidance improves semantics beyond the schema alone, justifying a 4.

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 purpose: 'Call a ReefAPI engine action — POST /<engine>/v1/<action> with params.' It specifies the HTTP method, resource (engine action), and parameters. It distinguishes itself from sibling tools like get_engine_schema (which provides schemas) and search_engines (which lists engines). The verb 'call' is specific 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description instructs to 'Get param names from get_engine_schema first,' indicating a prerequisite step. It also notes that 'Failed calls cost no credits,' which is a usage hint. However, it does not explicitly state when not to use this tool or provide alternatives to other sibling tools. The context is clear but lacks exclusionary guidance.

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