Skip to main content
Glama

cachly — Explain it once. Every AI knows it.

team_recall

Recall lessons from a shared team brain, showing who learned what. Works on any shared instance (all team members using the same instance_id). Shows author, recency, and severity for each lesson. Use this to onboard new team members or find who knows about a topic.

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": "team_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax lessons to return (default: 10)
topicNoTopic or keyword to filter lessons (optional)
authorNoFilter by author name (optional)
instance_idNoUUID of the shared team brain instance

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?

With no annotations at all, the description carries the full disclosure burden. It does add real value by describing the per-lesson fields returned (author, recency, severity) and the cross-member sharing model, but it never confirms this is a non-mutating read, nor mentions permissions to access a shared instance or what happens if instance_id is omitted.

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?

Four short sentences, front-loaded with what the tool does and immediately followed by scope and return contents. The opening "showing who learned what" is partly repeated by the later "Shows author, recency, and severity," a small redundancy in an otherwise tight description.

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 four-parameter, read-style tool with no annotations and no output schema, the description covers the essentials: shared-instance scope, filters by topic/author implied, and the shape of each returned lesson. Only edge behavior — missing instance_id, empty results, access restrictions — is left unaddressed.

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 limit, topic, author, and instance_id are all already documented in the input schema. The description contributes only one extra semantic detail — that instance_id identifies the shared team instance all members use — which is helpful but modest; the return fields it lists are not parameters.

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?

"Recall lessons from a shared team brain, showing who learned what" gives a specific verb (recall), resource (lessons), and scope (shared team brain), and the emphasis on "team" implicitly separates it from single-user recall tools like recall_context. It stops short of naming the sibling it should be preferred over, so an agent still has to infer the split from the word "team".

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?

"Use this to onboard new team members or find who knows about a topic" states concrete situations, and "Works on any shared instance (all team members using the same instance_id)" clarifies the prerequisite for shared data. There is no explicit when-not guidance (e.g. use team_learn to write lessons, use recall_context for personal memory), which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.