Skip to main content
Glama
Sign In

VolatiAI MCP

by io.github.christianscode1994
OverviewDiscussionsAdmin

get_sector

Get current data for one sector. Sector slugs from list_active_signals output.

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": {
      "sector": "<sector>"
    },
    "name": "get_sector"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYese.g. nvd-new-cves-count, kraken-btc-usd

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a read via "Get" but never states that the call is non-mutating, whether results are live or cached under "current," or how invalid slugs fail.

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 short sentences, purpose first and the slug-source hint second, with no filler. Nothing is wasted, though it is also close to the minimum needed.

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 one-parameter tool with a fully documented schema this is close to adequate, but with no output schema the description should say what "current data" looks like so the agent knows what it will receive. Error behavior for a bad slug is also unaddressed.

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

Parameters3/5

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

Schema coverage is 100% and the schema already gives example slugs, so the baseline is 3. The description adds the useful provenance hint that valid slugs come from list_active_signals output, but no format or matching rules beyond that.

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 ("Get") and resource ("current data for one sector"), and ties the tool to the sibling list_active_signals as the slug source, which helps separate it from list_categories and list_active_signals. The only weakness is that "current data" doesn't say what data (a count, a price, a signal value) is returned.

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?

It gives one concrete usage dependency: sector slugs come from list_active_signals output, which is genuinely useful routing. It does not say when to prefer find_corroborations, get_current_revision, or verify_snapshot, nor what happens if the slug is stale or invalid.

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

All VolatiAI MCP 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