Skip to main content
Glama

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 accepts an OAuth access token (connect with OAuth and paste your key once on the consent screen — this is what ChatGPT uses), an Authorization: Bearer <key> header, x-reefapi-key, or the key in the connection URL (https://api.reefapi.com/mcp?key=<key>). Get a key at https://reefapi.com. Failed calls cost no credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engine": "<engine>",
      "action": "<action>"
    },
    "name": "call_engine"
  }
}

Input 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.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the return envelope ({ ok, data, meta, error }), the full auth matrix for local vs hosted servers, and the cost behavior ('Failed calls cost no credits'). Annotations only say non-readonly, open-world, non-idempotent, non-destructive; the description adds the operationally important context.

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?

The core action and endpoint are front-loaded in the first clause, which is the right structure. The long enumeration of auth mechanisms and URLs is dense but each item is actionable, though it could have been compressed.

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?

With no output schema, the description correctly supplies the return envelope shape, and it covers auth and credit behavior for a mutation-capable tool. The one gap is the contradictory pointer to get_engine_schema versus get_action_schema for parameter discovery.

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 description coverage is 100%, so each of the three parameters is already documented with examples in the schema. The description adds only the framing that `params` is the POST body; it does not elaborate further. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Call a ReefAPI engine action') plus the exact transport shape (POST /<engine>/v1/<action> with `params`). That is clearly distinguishable from the sibling schema/catalog/discovery tools, which only return metadata.

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?

Gives an explicit prerequisite ordering ('Get param names from get_engine_schema first', and a pointer for obtaining a key), which is real usage guidance. It stops short of stating when NOT to call it, and the referenced sibling name conflicts with the schema's 'get_action_schema' reference, which muddies the routing advice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources