Skip to main content
Glama
Sign In

User Intuition

by ai.userintuition
OverviewDiscussionsAdmin

View Research Answer

view_research_answer
Read-onlyIdempotent

Show the full answer in this MCP chat with clickable verified quotes and original recordings. Use this to display the answer after research chat, rather than linking to an external dashboard. Use after chat_research_session or queue_research_chat; pending jobs can be checked here. Keep session_id and job_id for follow-ups. Set reference_label to read one cited quotation and its transcript/recording context. Preserves backend citation labels; never invent sources.

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": {
      "session_id": "<session_id>",
      "job_id": "<job_id>"
    },
    "name": "view_research_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesIdentifier returned when the background job was queued.
session_idYesUUID of the research session, as returned by inspect_research_session.
organization_idNoOrganization for this operation and billing. Use list_organizations to choose an active membership.
reference_labelNoCitation label from the saved answer, such as 1 or D1.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / job_id / description
      Added value: +"Identifier returned when the background job was queued."
    • addedInput schema / properties / reference_label / description
      Added value: +"Citation label from the saved answer, such as 1 or D1."
    • addedInput schema / properties / session_id / description
      Added value: +"UUID of the research session, as returned by inspect_research_session."
  2. Changed1 schema field changed
    • changedInput schema / properties / organization_id / description
      Previous value: -"Platform admins only: select an organization for this operation. Required when changing another organization’s study or using its wallet."New value: +"Organization for this operation and billing. Use list_organizations to choose an active membership."
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered structurally. The description adds genuine behavior beyond that: it works on pending jobs as well as completed ones, and it preserves backend citation labels rather than synthesizing sources. It does not describe what happens if the job failed or is still running beyond 'can be checked here'.

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 primary action, then usage, then the optional narrowing parameter. Five short sentences with no filler, though the instruction list is dense enough that the reference_label detail could be separated for easier scanning.

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?

An output schema exists, so return values need no explanation. Given a read-only tool with 4 fully documented parameters, the description covers placement (in-chat vs dashboard), prerequisites (which tools precede it), follow-up key retention, and citation-integrity expectations.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds real meaning beyond the schema for reference_label ('read one cited quotation and its transcript/recording context') and warns to retain session_id and job_id for follow-ups, which the schema does not convey.

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 first sentence states a specific verb and resource (show the full answer) plus concrete rendering traits (clickable verified quotes, original recordings), and explicitly contrasts with 'linking to an external dashboard'. An agent can distinguish this from answer_research or get_research_analysis without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit sequencing ('use after chat_research_session or queue_research_chat'), states that pending jobs can be checked here, names the alternative it replaces (external dashboard), and explains which parameter to set to narrow to one citation. When-to-use and the follow-up path are both spelled out.

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

All User Intuition toolsInspect
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.

Resources