OpenDont

Ask a question

ask_question

Idempotent

When the user needs a sourced answer that this network does not have yet (search first), publish the question so it can be answered for everyone. It is published at once as unverified community content; reported content is reviewed by a moderator. Write a self-contained, general question without personal data.

Input Schema

Name	Required	Description
`body`	Yes	Context and what a good answer must cover
`title`	Yes	The question, 10-240 characters
`language`	Yes	BCP-47 language of the text, e.g. en or pt-BR
`topic_tags`	No	Up to 8 lowercase-hyphenated topics, e.g. from browse_knowledge
`source_context`	No	Where the question comes from

Output Schema

Name	Required	Description	Default
`notice`	Yes
`status`	Yes
`entity_id`	Yes
`public_url`	No
`request_id`	Yes
`status_url`	Yes
`entity_type`	Yes
`submission_id`	Yes
`content_license`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026
- addedOutput schema / properties / public_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedOct 25, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that content is published immediately, is labelled unverified community content, is subject to moderator review when reported, and must be self-contained without personal data. The annotations only say this is a non-read-only, non-destructive, open-world-false write; the description supplies the actual publication and moderation semantics an agent needs.

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 sentences: the first front-loads the trigger and the effect, the second covers publication status, moderation, and content constraints. No sentence is redundant and nothing is buried.

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?

An output schema exists and annotations carry the safety profile, so the description's job is the publishing semantics, which it covers. The one gap is duplicate handling implied by the idempotentHint=true annotation – the description doesn't say whether re-asking an existing question is deduplicated or creates a new post.

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, but the description adds real guidance for the required title/body content ('self-contained, general question without personal data') that constrains what to write. It does not address topic_tags or the source_context enum values beyond the schema's own descriptions.

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 ('publish the question') plus the outcome ('so it can be answered for everyone'), which separates it from the retrieval siblings browse_knowledge/search_knowledge that the 'search first' clause implies. It never names a sibling tool directly, so differentiation is inferred rather than explicit.

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 a clear triggering condition ('when the user needs a sourced answer that this network does not have yet') and a pre-condition ('search first'), which effectively routes the agent away from this tool when content already exists. It stops short of naming the specific alternative tools or explaining what to do after publishing.

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

All OpenDont 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?