Skip to main content
Glama
Sign In
tech-recall

tech-recall

by WItaZhang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_recommendation

Read-only

Reads the current card and task-local source verification cache when a user expands a recommendation, returning the stored context needed for review.

Instructions

On user expansion, read the current card and task-local source verification cache.

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": {
      "recommendation_id": "<recommendation_id>",
      "task_id": "<task_id>"
    },
    "name": "get_recommendation"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
recommendation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds that it reads both the current card and a task-local verification cache, but it does not explain behavior around cache misses, permissions, or error handling.

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 a single, front-loaded sentence with no wasteful clauses. Its brevity is appropriate, though the phrase 'On user expansion' is somewhat opaque and could be clarified without adding much length.

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

Completeness2/5

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

Given two required undocumented parameters and a non-obvious relationship between the tool name and the described read operation, the definition is under-specified. The output schema and annotations reduce the burden somewhat, but an agent still lacks enough context to use this tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for two required parameters, recommendation_id and task_id. The description mentions 'task-local' but never explains what either parameter identifies, how they relate, or what format they expect, so it fails to compensate for the missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('read') and resources ('current card and task-local source verification cache'), but it does not clearly connect these to the tool name 'get_recommendation'. It also fails to distinguish this read from the sibling tool 'get_card', which likely reads a card too.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'On user expansion' provides an implied usage trigger. However, it does not explain when to choose this tool over alternatives such as get_card, expand_recommendation, or recall_candidates, nor does it state any when-not conditions.

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

Deploy Server

Other Tools