Veritula

Search discussions

search_discussions

Read-onlyIdempotent

Searches the public discussions on Veritula by their titles and descriptions, those with the query's words in their titles first. Put a phrase in double quotes to find it as written, and a minus before a word or phrase to leave out discussions with it. Without a query, lists the discussions most recently active. Chronicles retell discussions that took place before Veritula. get_discussion gives a discussion's ideas.

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": "search_discussions"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	20 results per page, starting at 1
`query`	No	The words to search for

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world semantics, so the description correctly spends its words elsewhere: query syntax (quoted phrases, minus-prefixed exclusions), result ordering, and the no-query fallback. The one weak spot is the 'Chronicles retell discussions that took place before Veritula' sentence, which does not make clear whether Chronicles are included in results or are a separate concept.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and syntax rules are front-loaded and earn their place. However, the Chronicles sentence is vaguely worded and interrupts the flow between search syntax and the `get_discussion` pointer, costing clarity in an otherwise tight description.

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 two-parameter, read-only search with no output schema and full schema coverage, the description supplies the missing pieces an agent needs: syntax, ranking, and default behavior. Only the ambiguous Chronicles reference and the absence of any hint about result shape leave a small gap.

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 schema already documents both parameters and the 20-per-page paging rule. The description nonetheless adds real meaning beyond the schema's bare 'The words to search for' by explaining quoted-phrase matching, exclusion syntax, and what an omitted query does.

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 ('Searches the public discussions on Veritula') plus the fields searched (titles and descriptions) and the ranking rule (title matches first). It also distinguishes itself from the sibling `get_discussion`, so an agent can separate discovery from retrieval without opening schemas.

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 default mode ('Without a query, lists the discussions most recently active') and a follow-up route to `get_discussion` for detail. It does not explicitly contrast with `search_ideas`, so the agent must infer from the resource name that discussions and ideas are searched by different tools.

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

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