Skip to main content
Glama
Sign In

Andru

by io.github.geter-andru
OverviewDiscussionsAdmin

Search what Andru remembers

get_revenue_memory
Read-only

What Andru has learned about their buyers and deals: use this when the person asks what they decided, learned or recorded before: metrics, deal patterns, account history, decisions and habits Andru has saved. Filter by category, key pattern or memory type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_revenue_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoFilter to a specific memory category. Omit to search all.
keyPatternNoFilter keys matching this pattern (supports * wildcards, e.g., "*mrr*", "acme_*").
memoryTypeNoFilter by memory type. episodic=specific facts, semantic=patterns, procedural=behavioral habits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and scope profile is covered. The description adds useful domain context about what kinds of memories exist, but it does not describe result shape, pagination, or how broad the search is.

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?

The description is compact and front-loads both the resource and the primary usage trigger. The colon-heavy phrasing is slightly awkward, but it remains efficient and every clause contributes information.

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 retrieval tool with fully documented parameters and read-only annotations, the definition is adequate. However, with no output schema, it would be stronger if it described the returned result shape and clarified its relationship to get_memory_history.

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%, so all three filter parameters are fully documented in the schema, including enums and wildcard support for keyPattern. The description only restates that filtering is possible by category, key pattern, or memory type, adding no syntax or semantics beyond the schema.

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?

The description states a clear retrieval purpose: surfacing what Andru has saved about buyers and deals, including metrics, deal patterns, account history, decisions, and habits. It is more specific than the title and name alone, but it does not explicitly distinguish itself from the close sibling get_memory_history.

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?

It gives an explicit usage trigger: 'use this when the person asks what they decided, learned or recorded before.' That is clear guidance for selection, but it names no exclusions or alternatives, such as when to use get_memory_history instead.

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

All Andru 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