Skip to main content
Glama
Sign In

Veritula

by com.veritula
OverviewDiscussionsAdmin

Get an idea

get_idea
Read-onlyIdempotent

Gets an idea, criticism or comment on Veritula by its number (#123 on the site): its full text in Markdown, whether it's rationally adoptable, what it replies to, and the replies it got: its pending criticisms (the ones that keep it from being rationally adoptable), the criticisms that have been addressed by pending criticisms of their own, and neutral comments. Replies are given in brief; get them in full by their numbers.

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": {
      "id": "<id>"
    },
    "name": "get_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe idea’s number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety bar is low. The description adds genuinely new behavioral context: replies are truncated to brief form and must be re-fetched by number, plus the categorization of replies (pending criticisms, addressed criticisms, neutral comments). It does not mention permissions or failure behavior, which is minor for a read-only tool.

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?

One dense sentence that front-loads the action and then enumerates returns and follow-up guidance; almost no waste. The semicolon-heavy structure makes it slightly harder to scan than a short bulleted breakdown would be.

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?

There is no output schema, so the description must carry return-value expectations, and it does so concretely (full Markdown text, rational adoptability, reply structure). Remaining gaps – error cases and whether replies can be paginated – are minor for a single-parameter read tool.

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% and the single parameter is already documented as 'The idea's number.' The description nonetheless adds the on-site format convention ('#123 on the site'), which is real meaning beyond the schema.

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 ('Gets an idea, criticism or comment on Veritula by its number') and enumerates what is returned, so the agent knows this is a single-item fetch. It does not name siblings such as search_ideas or get_discussion, but 'by its number' implicitly separates it from search-style tools.

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?

Includes an explicit routing instruction for follow-up work: 'Replies are given in brief; get them in full by their numbers,' telling the agent to call this tool again for detail. It gives no explicit when-not-to-use or alternatives, but the usage context is clear.

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

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