Skip to main content
Glama

Virustotal

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (idempotent hint), description adds critical behavioral traits: persistence for authenticated users, 24-hour retention for anonymous, and key-value scoping. No contradiction with annotations.

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?

Four sentences, front-loaded with purpose. Each sentence provides essential information without redundancy. Highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter tool with no output schema, the description covers purpose, usage, behavioral notes, and pairing. No gaps remain for agent understanding.

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 description coverage is 100%, so baseline is 3. Description provides example key patterns (subject_property, target_ticker) which adds some value but does not significantly expand beyond schema.

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?

The description clearly states the tool saves data for reuse, with a specific verb ('save') and resource ('data'). It distinguishes from sibling tools like recall and forget, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'when you discover something worth carrying forward'. It provides context on scoping, retention, and pairing with recall/forget, offering clear guidance.

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

All Virustotal toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

The set mixes several overlapping families: ask_pipeworx and ask_pipeworx_beta are described as currently identical, while ask_pipeworx_grounded, deep_research, bet_research, and validate_claim all route to the same underlying data sources. Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, spread) also blur together; only the four lookup_* VirusTotal functions are cleanly distinct.

Naming Consistency3/5

Names are uniformly snake_case with a few consistent families (lookup_domain/file/ip/url, ask_pipeworx_*, polymarket_*), which helps. However, the set mixes imperative verbs (remember, forget, subscribe, validate_claim), noun phrases (entity_profile, deep_research, recent_alerts), and inconsistent prefixes, so no single naming convention holds across the server.

Tool Count2/5

35 tools is too many for the apparent purpose, especially for a server named Virustotal. The bulk of the tools address unrelated Pipeworx research, memory, and prediction-market functions, so the count does not reflect the server's advertised domain.

Completeness1/5

For a VirusTotal server, only four lookup tools exist and there is no way to submit a URL/file, create a scan, retrieve analysis details, or explore relationships—core VirusTotal operations are missing. Scoped broadly, the unrelated Pipeworx tools are extensive, but they do not fill the gaps in the advertised domain. The surface is severely incomplete relative to the server name.

Resources