Skip to main content
Glama

AINDEX

Answer a step of your agent's check

agent_check_step

Answer the open step of a check from start_agent_check: the agent's tool calls (name and input, as the step's tools list gives them; several per step are fine), or text alone. AINDEX runs them as the agent's own (decide is checked and its orders placed under the owner's mode and limits) and returns the next step with the results, or how the check ended. With no calls, it waits for a step still being carried out. Needs an access key that may act.

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": {
      "agent": "<agent>",
      "check": "<check>"
    },
    "name": "agent_check_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepNoThe step waiting; left out, the one waiting on this check
textNo
agentYes
callsNo
checkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that AINDEX runs the supplied calls as the agent's own, that decide is checked and orders are placed under the owner's mode and limits, and that it returns the next step with results or how the check ended. It also notes the access-key requirement, adding meaningful behavioral context.

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 purpose is front-loaded, and each sentence contributes useful information about usage, execution, waiting behavior, or access requirements. There is little to no redundant wording.

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?

For a complex, mutating, step-based tool with no output schema, the description explains execution behavior, return shape at a high level, waiting semantics, and authentication needs. It is not exhaustive about every possible end state, but it is complete enough for an agent to call the tool correctly.

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 low at 20%, so the description must carry parameter meaning. It adds useful semantics for calls and text, such as accepting the agent's tool calls with names and inputs, allowing several per step, and permitting text alone. It does not explain the required agent and check parameters or fully elaborate the step parameter, leaving some gaps.

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: answer the open step of a check from start_agent_check. It clearly distinguishes this from starting a check and explains that the step may contain tool calls or text alone.

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 gives clear usage context: use it for an open step from start_agent_check, and with no calls it waits for a step still being carried out. It does not explicitly compare against alternative sibling tools, but the context is clear enough to select it correctly.

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