Skip to main content
Glama

Warframe

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
Behavior4/5

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

Annotations already indicate a write operation (readOnlyHint false) and idempotency (idempotentHint true). The description adds useful behavioral context beyond that: key-value storage scoped by identifier, retention details ('persistent memory' versus '24 hours' for anonymous), and the ability to pair with recall/forget. It does not explicitly state overwrite behavior on an existing key, but the idempotent hint partially covers that gap.

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?

The description is four sentences, each earning its place: purpose, usage, storage details, and companion tools. It is front-loaded with the main action and avoids wordiness while being comprehensive for the tool's simplicity.

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 is complete: it covers what the tool does, when to use it, persistence semantics, and how to retrieve/delete. No significant gaps remain for an agent to decide correctly.

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 each parameter already has a clear description ('key' with examples, 'value' with what to store). The tool description enriches this by giving real-world examples (resolved ticker, target address, user preference) and explaining the key-value pairing concept, adding value beyond the structured 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 opens with a specific verb and resource: 'Save data the agent will need to reuse later.' It clearly distinguishes the tool from siblings by explicitly pairing with 'recall to retrieve later, forget to delete,' and by mentioning cross-session persistence. This goes beyond a generic restatement of the name.

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?

The description gives explicit when-to-use guidance: 'Use when you discover something worth carrying forward' and lists concrete examples like a resolved ticker or user preference. It also contrasts authenticated vs. anonymous sessions and names alternative tools (recall, forget), making the decision context clear.

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

All Warframe 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.8/5.0
Disambiguation2/5

Many tools overlap in purpose: three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are nearly identical routers, five polymarket_* tools cover similar prediction-market ground, and the server combines a tiny Warframe component with a broad Pipeworx/Polymarket toolkit, making selection ambiguous. The server name 'Warframe' does not match the majority of tools, further muddying intent.

Naming Consistency3/5

There is a loose snake_case convention, and several tools follow a verb_noun pattern (get_fissures, list_subscriptions, search_items, validate_claim). However, single-word imperative tools (remember, recall, forget), noun-phrase names (entity_profile, world_state, deep_research), and the polymarket_* family using inconsistent second words break the pattern. It is readable but not cleanly predictable.

Tool Count2/5

35 tools is far too many for a Warframe-focused server, and only 4 tools (get_fissures, get_invasions, search_items, world_state) actually relate to Warframe. The remaining 31 tools are a sprawling generic data/research/prediction-market collection that belongs to a different product, making the set bloated and unfocused for its apparent purpose.

Completeness3/5

Relative to the Warframe domain, the coverage is thin: only fissures, invasions, item search, and a combined world_state are offered, with obvious gaps like alerts, news, Nightwave, and event tracking. The broader Pipeworx/Polymarket toolset is internally comprehensive, but those tools do not serve the server's stated name and leave the Warframe scope incomplete.

Resources