Skip to main content
Glama
dizzydes

0pi-mcp-server

by dizzydes

get_object

Retrieve stored data from cloud storage using its object ID. Access previously saved information across sessions or workflows for continued processing.

Instructions

Retrieve data from cloud storage using its ID. Use this to read data that another agent (or yourself) saved previously.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
object_idYesThe object ID (8-character identifier from the URL)

Implementation Reference

  • Tool handler for 'get_object', which retrieves data via the 'getWorkspace' function.
    if (name === 'get_object' || name === 'get_shared_workspace') {
      const { object_id, workspace_id } = args;
      const id = object_id || workspace_id;
    
      if (!id) {
        throw new Error('object_id is required');
      }
    
      const data = await getWorkspace(id);
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              success: true,
              data: data
            }, null, 2)
          }
        ]
      };
    }
  • Schema definition for the 'get_object' tool in the ListTools response.
    {
      name: 'get_object',
      description: 'Retrieve data from cloud storage using its ID. Use this to read data that another agent (or yourself) saved previously.',
      inputSchema: {
        type: 'object',
        properties: {
          object_id: {
            type: 'string',
            description: 'The object ID (8-character identifier from the URL)'
          }
        },
        required: ['object_id']
      }
    }
  • The helper function 'getWorkspace' that performs the API call to retrieve the object data.
    /**
     * Retrieve workspace data
     */
    async function getWorkspace(workspace_id) {
      try {
        const response = await axios.get(`${API_BASE_URL}/w/${workspace_id}`, {
          timeout: 5000
        });
    
        // Log successful retrieval
        logEvent('workspace_retrieved', {
          tool_name: 'get_shared_workspace',
          workspace_id
        });
    
        return response.data;
      } catch (error) {
        // Log error
        logEvent('workspace_retrieval_failed', {
          tool_name: 'get_shared_workspace',
          workspace_id,
          error: error.message
        });
    
        if (error.response?.status === 404) {
          throw new Error('Workspace not found or expired');
        }
        throw new Error(`Failed to retrieve workspace: ${error.message}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool is for reading/retrieving data, which implies it's non-destructive, but doesn't specify permissions, rate limits, error conditions, or what happens if the object ID is invalid. For a cloud storage tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is two sentences with zero waste—each sentence adds essential information (what the tool does and when to use it). It's front-loaded with the core purpose and efficiently structured without redundancy.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and usage but lacks details on behavioral aspects like error handling or return values, which are important for a cloud storage retrieval tool. Without annotations or output schema, more context would improve completeness.

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

Parameters3/5

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

The input schema has 100% description coverage, with the parameter 'object_id' documented as 'The object ID (8-character identifier from the URL)'. The description adds minimal value beyond this by mentioning 'using its ID' but doesn't provide additional context like format examples or constraints. This meets the baseline for high schema coverage.

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's purpose with specific verbs ('Retrieve data', 'read data') and identifies the resource ('cloud storage', 'using its ID'). It distinguishes from the sibling 'create_object' by focusing on retrieval rather than creation, though it doesn't explicitly name the sibling. The description avoids tautology by explaining functionality beyond the tool name.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('to read data that another agent (or yourself) saved previously'), which implicitly distinguishes it from the sibling 'create_object' for saving data. However, it doesn't explicitly state when not to use it or name alternatives, keeping it from a perfect score.

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/dizzydes/0pi-mcp-server'

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