Olothea — Collaborative Human–AI Research

research_submit_question

Unreviewed public question submission. Rejects exact duplicates; possible semantic relatives linked, not merged.

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": {
      "question": "<question>"
    },
    "name": "research_submit_question"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	No
`question`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With only readOnlyHint=false supplied, the description must carry the behavioral load, and it does add real value: submission is unreviewed, exact duplicates are rejected, and semantic relatives are linked rather than merged. That dedup/linking behavior is non-obvious and materially affects how an agent should call it. It stops short of saying what is returned or whether the caller needs an identity for the agent_id field.

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?

Two clauses, zero filler, and the key traits (unreviewed, duplicate rejection, linking) are front-loaded. The phrase 'linked, not merged' is compressed to the point of needing interpretation, which slightly undercuts the terseness benefit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a small three-parameter write tool with no output schema and minimal annotations, the description covers purpose and duplicate-handling behavior but leaves the entire parameter surface and the post-submission outcome (returned identifier, review queue, moderation delay) unexplained. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description should compensate, but it never mentions 'question', 'description', or 'agent_id' nor their formats, limits, or required status. The only clue is that duplicates are judged on the question text, which is weak inference rather than stated meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: submitting a public question that is 'unreviewed' (i.e. not validated before publication). The qualifier 'public question submission' separates it in spirit from sibling tools like research_submit_contribution, but it never names or contrasts with any sibling explicitly.

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?

'Unreviewed public question submission' implies the context of use (asking a question rather than answering or contributing), but there is no explicit when-to-use, when-not-to-use, prerequisite, or named alternative among the many research_* and workspace_* siblings. Guidance is implied only.

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

All Olothea — Collaborative Human–AI Research 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.

Resources

Need Help?