Skip to main content
Glama

Materials

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

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

Beyond annotations (idempotentHint, destructiveHint), the description adds scoping by identifier, persistence differences for authenticated vs anonymous sessions, and retention duration (24 hours). No contradictions.

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, efficiently conveying purpose, usage, behavior, and related tools. No unnecessary words; front-loaded with key information.

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?

Given a simple key-value store with no output schema, the description covers all necessary aspects: purpose, when to use, behavior, and relationship to sibling tools. Complete and self-contained.

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 already covers both parameters with descriptions. The description adds value by providing concrete examples (e.g., 'subject_property', 'target_ticker'), enhancing usability.

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 uses a specific verb ('Save') and resource ('data'), and clearly distinguishes from sibling tools like recall and forget by mentioning them as paired operations.

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?

Provides clear usage scenarios ('discover something worth carrying forward') with examples, but lacks explicit when-not-to-use guidance. Still above average.

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

All Materials 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
Disambiguation3/5

While many tools have detailed descriptions that help differentiate them, there is significant overlap among query tools like ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research. The prediction market tools also cluster together, making it challenging for an agent to quickly pick the right one without careful reading.

Naming Consistency4/5

Most tools follow a descriptive snake_case convention (e.g., ask_pipeworx, entity_profile, compare_entities). Minor deviations exist, such as 'ai_visibility_check' and 'deep_research', but overall the naming pattern is predictable and clear.

Tool Count3/5

With 33 tools, the server is larger than typical single-domain servers. While it supports a broad data platform, this count feels somewhat bloated and could benefit from consolidation, especially among overlapping query tools.

Completeness1/5

The server is named 'Materials' but contains only two materials-specific tools (materials_search, materials_stability). The remaining 31 tools cover unrelated domains (finance, economics, prediction markets, etc.), leaving the stated domain severely incomplete.

Resources