Vi Assistant by Vultax

get_research_article

Read-onlyIdempotent

Read a complete published Vultax study and its source metadata. This is historical research, not a current market snapshot.

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": {
      "slug": "<slug>"
    },
    "name": "get_research_article"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 27, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations fully cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description adds a genuinely useful behavioral trait: the retrieved content is immutable historical research rather than live data. It still says nothing about behavior on a missing slug or the volume of returned content.

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 tight sentences that front-load what is retrieved, followed immediately by the disambiguating temporal caveat. No wasted words.

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?

With no output schema the description must convey the return shape, and 'complete study and its source metadata' does so adequately for a single-item fetch tool. Minor gaps remain around error behavior for an invalid slug and whether the study body is paginated or truncated.

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% and the single 'slug' parameter is undocumented in both schema and description. The pattern '^[a-z0-9-]+$' and maxLength constrain the value but the description never explains where a slug comes from or how to obtain one, so it fails to compensate for the coverage gap.

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?

Names a specific verb (Read) and resource (a complete published Vultax study plus its source metadata), so the agent knows exactly what it retrieves. It implicitly separates itself from live-market tools via the 'not a current market snapshot' line, but never names a sibling like inspect_prediction_market or get_research_dataset directly.

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?

The phrase 'This is historical research, not a current market snapshot' implies the correct context of use and hints that live-market tools exist for the other case, but no alternative is named and no prerequisite or exclusion is stated explicitly. Usage is inferable rather than spelled out.

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

All Vi Assistant by Vultax 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.