Skip to main content
Glama

netcafe-memory

by com.ainetcafe

Find the right tool for a task

what_can_you_do
Read-onlyIdempotent

Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready-to-run example calls — instead of reading the whole catalogue and guessing. Also returns multi-step recipes when a task needs several tools chained (invoices to a ledger, a bank statement reconciled, a messy CSV turned into a deliverable). Deterministic and free: it calls no model, costs nothing, and never runs out of quota. Call this FIRST when you are not sure what this server offers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesWhat you are trying to do, e.g. "reconcile a bank statement against my books" or "把一堆发票整理成能入账的表格"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnlyHint and idempotent annotations, the description adds that the tool is deterministic, calls no model, costs nothing, and never runs out of quota. It also discloses that it returns ready-to-run examples and recipes, providing valuable behavioral context without contradicting 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?

The description is three sentences, front-loaded with the core action. Every sentence contributes value: purpose, output type, and usage guidance. There is no fluff or redundancy.

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?

The tool is simple (one parameter, read-only, output schema provided). The description covers purpose, usage, behavioral traits, and cost/quota characteristics, making it sufficiently complete for an agent to decide when to invoke it.

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?

The schema already fully documents the 'task' parameter with examples (100% coverage). The description adds the nuance that any language is accepted, which is a small but useful extension beyond the schema, warranting a score above the baseline of 3.

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's function: given a plain-language task, it returns the matching tools with example calls and multi-step recipes. It also distinguishes itself from sibling memory tools (forget/recall/remember) by focusing on tool discovery, so there is no ambiguity about what it does.

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 explicitly advises to 'Call this FIRST when you are not sure what this server offers', giving clear when-to-use guidance. It also contrasts with 'reading the whole catalogue and guessing', implying it should be preferred over manual exploration.

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

All netcafe-memory 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

A4.3/5.0
Disambiguation5/5

The four tools are role-distinct: remember writes, recall reads, forget deletes, and what_can_you_do is a discovery/help tool rather than a memory operation. No two tools could plausibly be selected for the same task.

Naming Consistency4/5

The three core memory operations follow a clear single-verb lowercase pattern (remember/recall/forget). The helper what_can_you_do breaks that pattern, but the divergence is obvious and unlikely to mislead.

Tool Count4/5

Four tools is a reasonable size for a small memory service: the three core operations plus one discovery helper. The count could feel slightly thin, but every included tool has a distinct function.

Completeness4/5

The memory lifecycle is covered for the most part: durable facts can be stored, retrieved, and permanently deleted. The main gap is the lack of an update/edit operation, though forget-and-remember is a viable workaround.

Resources