Skip to main content
Glama

get_action_schema

Read-onlyIdempotent

FULL detail for ONE engine action: every parameter (type, required, description, allowed_values dropdown, default, example, min/max), what it returns, pricing, and a ready-to-run example_params. Call this right before call_engine so you send valid params — invalid enum values are rejected with the allowed list.

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": "get_action_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesThe action's name on that engine (from get_engine_schema, e.g. 'search'). Returns the full param detail (type, required, allowed_values, default, example, min/max), what it returns, pricing, and ready-to-run example_params.
engineYesThe engine's name (e.g. 'zillow'), as returned by search_engines or get_catalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive lookup. The description adds useful behavioral context beyond annotations: it discloses validation behavior for invalid enum values and previews the returned detail, including pricing and ready-to-run example_params. It does not cover auth or rate limits, but those are less central for a schema lookup.

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 two focused sentences, front-loaded with what the tool returns and followed by the workflow instruction. Every sentence earns its place by adding either scope or usage rationale.

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 low-complexity read-only lookup with two fully documented parameters and rich annotations, the description is complete enough. It explains what the returned schema detail includes and how to use it before call_engine, leaving no critical gap for correct invocation.

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%, and both parameters are already well documented in the schema, including examples and source tools. The description adds little parameter-level meaning beyond emphasizing ONE engine action and the enum rejection behavior, so the baseline of 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb and resource: get full detail for ONE engine action, including exact contents such as parameters, return info, pricing, and example_params. It distinguishes the tool from get_engine_schema by focusing on an action rather than an engine, and from call_engine by positioning itself as the pre-call lookup step.

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?

It explicitly says to call this right before call_engine so the agent sends valid params, and it explains why: invalid enum values are rejected with the allowed list. It names call_engine as the downstream action, but does not explicitly state when not to use this tool, such as when the caller already knows the params.

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