Skip to main content
Glama

Get object

get_object
Read-onlyIdempotent

Everything the memory knows about ONE object: its properties, its incoming AND outgoing relationships grouped by type, the actions that touch it, and its APPROVED owners.

`memory` is the slug from list_my_memories; `object_id` comes from
semantic_search, list_objects or recall. An id that
belongs to a different memory 404s rather than resolving — ids are not
portable between memories, so re-resolve a name instead of reusing an id
you saw elsewhere.

Reach for something else when: you want the first ring around several
hits at once (semantic_search with expand=1 — one call, not one per hit);
you want how two objects connect (get_paths); you want what a change here
would disturb (get_change_impact).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoryYes
object_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: cross-memory ids 404 instead of resolving, ids are not portable, and only APPROVED owners are returned. It does not cover pagination or result-size limits, so not a 5.

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?

Three tight paragraphs, each load-bearing: what is returned first, then parameter provenance plus the 404 rule, then alternative routing. No filler sentences.

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?

An output schema exists, yet the description still previews the returned shape, and it closes the remaining gaps for an agent: parameter provenance, a failure mode, and sibling routing. Nothing needed to call it correctly is missing.

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?

Schema coverage is 0%, so the description must compensate and largely does: 'memory' is sourced from list_my_memories, 'object_id' from semantic_search/list_objects/recall, plus the non-portability rule for ids. It omits type constraints (integer vs string) that the schema carries, hence 4 rather than 5.

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+resource with enumerated scope: properties, incoming AND outgoing relationships grouped by type, touching actions, and APPROVED owners. This is distinguishable from siblings like get_paths and semantic_search without opening any 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?

Explicit routing section: 'Reach for something else when' names three alternatives (semantic_search expand=1 for multi-hit first ring, get_paths for connectivity, get_change_impact for blast radius) with the condition that selects each. Nothing is left to inference.

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.

Resources