Skip to main content
Glama

Get CloneAI Survey Result or Latest 3h Public Demo

cloneai_get_survey_result
Read-onlyIdempotent

Fetch the status or completed result of a synthetic persona survey job; omit the job ID to retrieve the current public demo result.

Instructions

Fetch the status or completed result of a survey job (omit job_id to fetch the latest 3-hourly public demo survey). This result is a response simulation by synthetic personas. It is not a survey of real people and does not represent public opinion. (Latest public 3h demo slot: 2026-11-13T00:00+09:00)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cloneai_get_survey_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNobrief is compact and meant for AI agents.brief
job_idNoJob ID (job_...) from cloneai_synthetic_persona_survey. Omit for the latest public demo.
api_keyNoapi_key.secret that owns the job (or send Authorization: Bearer). Required with job_id.
wait_secondsNoSeconds to wait for completion before returning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-obvious context: the output is a synthetic-persona simulation, not real respondents and not public opinion, which an agent must not misreport. It does not say what status values are returned or how wait_seconds interacts with completion, leaving some behavioral opacity.

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?

Front-loaded with the core action, followed by the demo-mode branch and the critical synthetic-data caveat; every sentence carries weight. The trailing parenthetical pinning a specific demo slot timestamp ('2026-11-13T00:00+09:00') is time-sensitive trivia that can go stale and slightly dilutes the otherwise tight structure.

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 read-only fetch with no output schema, the definition covers both invocation modes, the auth requirement is in the schema, and the synthetic-simulation disclaimer prevents the most likely misuse. What remains uncovered is the shape/meaning of returned status values and whether repeated polling is expected, which matters for an agent deciding how to consume the response.

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 coverage is 100% and every parameter (format, job_id, api_key, wait_seconds) is described in the schema itself, so the baseline is 3. The description reinforces the job_id-omission semantics but adds no format, auth, or wait_seconds detail beyond what the schema already states.

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 ('Fetch the status or completed result of a survey job') and immediately covers the two invocation modes: with a job_id, or the latest 3-hourly public demo. The read/fetch scope is cleanly separable from the sibling that creates surveys (cloneai_synthetic_persona_survey), which the schema references.

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 clear conditional guidance for the main branch point: 'omit job_id to fetch the latest 3-hourly public demo survey'. What is missing is guidance on when to call it repeatedly to poll versus when a result is final, and no explicit statement of when not to use it.

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