Skip to main content
Glama
Sign In

Andru

by io.github.geter-andru
OverviewDiscussionsAdmin

Save what a deal taught

log_revenue_insight

Writing down what each deal taught: use this when the person asks you to remember something about their buyers or deals: a deal decision, a reason a deal was won or lost, an ICP refinement, a metric update or a strategic pivot. Saving an existing key keeps the previous value in its history.

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": {
      "category": "<category>",
      "key": "<key>",
      "value": "<value>"
    },
    "name": "log_revenue_insight"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesUnique identifier for this memory (lowercase_underscored, e.g., "current_arr", "acme_deal_stage").
valueYesThe memory content — a concise, specific fact or insight.
domainNoBusiness domain this memory relates to. Default: general.
categoryYesWhat kind of memory this is.
confidenceNoHow confident this memory is (0.0-1.0). Default: 1.0 for founder-stated facts.
memoryTypeNoepisodic=time-bound fact, semantic=general pattern, procedural=behavioral habit. Default: episodic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already indicate this is a non-read-only, non-destructive, open-world write operation. The description adds useful behavioral context beyond the annotations by noting that saving an existing key preserves the previous value in history, which signals upsert/history behavior.

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 front-loaded with the core idea and then gives a colon-delimited list of relevant example cases followed by the history-retention behavior. It is compact and mostly efficient, though the sentence structure is somewhat run-on.

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

Completeness4/5

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

For a six-parameter write tool with no output schema, the description covers the intended usage and the key non-destructive history behavior. It does not mention retrieval companions such as get_revenue_memory, but that is not necessary for correct invocation.

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 all six parameters including key, value, domain, category, confidence, and memoryType are already documented in the schema. The description illustrates the kinds of content to save, but it does not add parameter-level meaning beyond the schema baseline.

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 specific action, writing down deal-related memory, and gives concrete examples such as deal decisions, win/loss reasons, ICP refinements, metric updates, and strategic pivots. It is clear what the tool does, though it does not explicitly distinguish itself from sibling retrieval tools like get_revenue_memory or 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 clearly says to use the tool when the person asks the agent to remember something about buyers or deals, with several examples of the kinds of facts to save. It does not state when not to use it or explicitly point to retrieval alternatives, so it stops short of full alternative-routing guidance.

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