DeepMiro

Interview Agent

interview_agent

Read-only

Interview a simulated AI agent to uncover its perspective and reasoning, predicting behavior in community simulations.

Instructions

Chat with a specific simulated agent to understand their perspective, reasoning, and predicted behavior. The agent responds in character based on their persona and simulation experience.

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": {
      "simulation_id": "<simulation_id>",
      "agent_id": "<agent_id>",
      "message": "<message>"
    },
    "name": "interview_agent"
  }
}

Input Schema

Name	Required	Description
`simulation_id`	Yes	The simulation ID
`agent_id`	Yes	The agent's numeric ID within the simulation
`message`	Yes	Question or prompt to send to the agent
`platform`	No	Which platform persona to interview. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 13, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint true and destructiveHint false. The description adds that the agent responds in character, but does not disclose any additional behavioral traits such as rate limits or session behavior.

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 concise sentences, front-loaded with purpose, no extraneous information.

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?

Given the tool is a simple chat interface with annotations and schema coverage, the description adequately conveys core functionality. No output schema exists, but the response behavior is implied.

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?

Input schema has 100% description coverage for all 4 parameters. The description restates the overall purpose but adds minimal parameter-specific meaning beyond the 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 the verb 'chat' and the resource 'specific simulated agent', with a clear purpose to understand perspective, reasoning, and predicted behavior. It distinguishes from siblings like create_simulation or get_report.

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 implies usage context by stating the agent responds in character based on persona and simulation, but lacks explicit when-not-to-use or alternative tool comparisons. Clear context, no exclusions.

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

Deploy Server