Skip to main content
Glama

get_from_object_store

Fetch an object from the object store using its id and optional nested path to retrieve specific data.

Instructions

Use this tool to fetch an object from the object store.

You can fetch a specific object by using the object's id (e.g. @obj_001). You can also fetch any nested path by using the path-parameter (e.g. {"object_id": "@obj_001", "path": "user_info.given_name"} -> returns the content at obj.user_info.given_name).

:param object_id: The id of the object to fetch in the format @obj_001. :param path: The path of the object to fetch in the format of access.to.attr or ["access"]["to"]["attr"].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYes
pathNo
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It explains fetching and nested access but does not mention side effects, permissions, rate limits, or return format beyond a single example. The return structure is not fully described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but includes a docstring-style ':param' lines which add redundancy. It is front-loaded with purpose and examples, but could be shortened.

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?

The description lacks details on error behavior, return format (since no output schema), and constraints. For a tool with only 2 parameters and no annotations, it should cover more behavioral context.

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

Parameters5/5

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

Schema coverage is 0%, but the description adds detailed semantics for both parameters: object_id format '@obj_001' and path formats with examples. This fully compensates for the lack of schema descriptions.

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 fetches an object from the object store, with specific usage via object_id and optional path for nested content. This distinguishes it from siblings like get_slice_from_object_store.

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 description provides examples of how to use the tool but lacks guidance on when to use it versus alternatives (e.g., get_slice_from_object_store). No explicit when-not-to-use or selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deepset-ai/deepset-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server