Omnara

Resolve agent interaction

agents_interactions_resolve

Answers an open permission prompt or question so the paused agent resumes, and returns the resolved interaction. Send one answer per question with zero-based option_indices; permission prompts use 0 for Allow and 1 for Deny.

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": {
      "agentID": "<agentID>",
      "answers": "<answers>",
      "interactionID": "<interactionID>",
      "orgID": "<orgID>",
      "projectID": "<projectID>"
    },
    "name": "agents_interactions_resolve"
  }
}

Input Schema

Name	Required	Description
`actor`	No	External actor to attribute to the generated interaction_response agent input, upserted by (provider_tenant_id, provider_user_id) atomically with the resolution; a rejected request writes no actor. Only allowed for non-user principals; requests authenticated as a user must omit it and are attributed to the user's omnara actor. When a non-user request omits it, the generated input has no actor attribution.
`orgID`	Yes	Organization ID (org_...).
`agentID`	Yes	Agent ID (agt_...).
`answers`	Yes
`projectID`	Yes	Project ID (proj_...).
`interactionID`	Yes	Interaction ID (int_...).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / actor / description

Previous value: -"Identity and attributes of an external actor. Actors are upserted by (provider_tenant_id, provider_user_id) with the external provider. Omitted attributes keep their stored values; provided attributes are overwritten, including empty values. omnara actors are implicit and hosted integrations own their own actor identities."New value: +"External actor to attribute to the generated interaction_response agent input, upserted by (provider_tenant_id, provider_user_id) atomically with the resolution; a rejected request writes no actor. Only allowed for non-user principals; requests authenticated as a user must omit it and are attributed to the user's omnara actor. When a non-user request omits it, the generated input has no actor attribution."

Changed4 schema fields changedOct 17, 2026
- addedInput schema / properties / agentID / description
```
Added value: +"Agent ID (agt_...)."
```
- addedInput schema / properties / interactionID / description
```
Added value: +"Interaction ID (int_...)."
```
- addedInput schema / properties / orgID / description
```
Added value: +"Organization ID (org_...)."
```
- addedInput schema / properties / projectID / description
```
Added value: +"Project ID (proj_...)."
```
First observedOct 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations cover non-readOnly, non-destructive, non-idempotent and openWorld, and the description adds substantive detail that the annotations do not: the agent resumes, an interaction is returned, and one answer is sent per question. It does not mention what happens on re-resolving an already-resolved interaction, which is the main remaining gap for a non-idempotent mutation.

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 tightly written sentences, front-loaded with the action and outcome, followed by the answering convention. Nothing is redundant or padded.

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 6-parameter nested mutation with no output schema, the description covers the action, effect, and answer encoding, and the complex actor parameter is thoroughly documented in the schema. Error/conflict behavior on repeated resolution and the notion of a per-question answer ordering relative to the interaction are the only things an agent might still want.

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?

With schema coverage at 83%, the baseline is 3, but the description genuinely adds meaning beyond the schema: option_indices are zero-based, exactly one answer is sent per question, and permission prompts map 0=Allow, 1=Deny – none of which is expressed by the bare integer array 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?

The description states a specific verb and resource (answering an open permission prompt or question), names the effect on the agent (the paused agent resumes), and describes the return (the resolved interaction). This clearly separates it from siblings like agents_input or agents_interactions_list without needing their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It implies the usage condition – there must be an open prompt/question – but never states how to discover pending interactions (e.g. via agents_interactions_list) or when agents_input would be the better choice. Usage is inferable but not explicitly routed.

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

All Omnara tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.