Skip to main content
Glama

get_from_object_store

Fetch an object from the object store using its ID, with optional support for nested path retrieval.

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, and the description only explains the basic input mechanics. It does not disclose any behavioral traits like read-only nature, side effects, rate limits, or error conditions.

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 front-loaded with the purpose and includes efficient param documentation. Every sentence adds value, though it could be slightly more concise.

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

Completeness3/5

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

For a simple fetch tool, the description covers input semantics well but lacks output format details and does not differentiate from similar tools. Context for choosing this tool over siblings is missing.

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?

Despite 0% schema description coverage, the description thoroughly explains the object_id format (@obj_001), path format (dot or bracket notation), and provides complete usage examples, fully compensating for the schema's lack of detail.

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?

The description clearly states the tool fetches an object from the object store, with specific examples for object_id and path. However, it does not differentiate from siblings like get_slice_from_object_store or grep_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 scenarios: fetching by id and fetching nested paths. It does not include when not to use or mention alternatives, leaving usage guidance implicit.

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