Skip to main content
Glama
Sign In
DanceNitra

inspeximus

by DanceNitra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_as

Fetch one memory's full record as a named agent, enabling a scoped search hit to be read in full without exposing other records or revealing whether an unknown ID exists.

Instructions

Fetch ONE memory's full record AS a named agent -- the scoped companion to get, so an agent that found a hit through recall_as can read it in full without the unscoped get handing it back the whole store's records by id. Returns {} when the id is unknown OR the agent has no access; those two cases are deliberately indistinguishable, so this cannot be used to probe for the existence of a record.

Input Schema

NameRequiredDescriptionDefault
idYes
agentYes
include_quarantinedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.20.0
    • addedInput schema / properties / include_quarantined
      Added value: +{
+  "default": false,
+  "title": "Include Quarantined",
+  "type": "boolean"
+}
  2. Addedv2.20.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it delivers real behavioral value: it defines the return contract ({}) for both the unknown-id and no-access cases and explains that they are deliberately indistinguishable to prevent existence probing. It does not cover permission requirements in detail or the quarantined-visibility 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?

Two sentences, front-loaded with the core action and scoping before the return-contract nuance. Slightly dense with backticked sibling references, but no wasted filler.

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?

No output schema and no annotations, so the description must do everything; it covers access scoping and the empty-object return contract well. The unexplained `include_quarantined` flag is the one meaningful gap for an agent calling this correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry all three parameters. It implies the `agent` scoping effect and the `id` lookup, but `include_quarantined` is never mentioned, so one parameter is entirely undocumented in both the schema and the prose.

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?

States a specific verb and resource ('Fetch ONE memory's full record AS a named agent') and immediately distinguishes itself from the sibling `get` by naming it as the 'scoped companion'. An agent can tell exactly which tool to pick without opening either schema.

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?

Explicitly ties usage to a workflow ('an agent that found a hit through `recall_as` can read it in full') and names the condition that selects the alternative ('without the unscoped `get` handing it back the whole store's records'). When-to-use and the alternative are both stated.

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