Skip to main content
Glama

aps_get_item_details

Retrieve summarized metadata for a single file or item, including name, type, size, version, and dates, using a project ID and item ID for quick lookups.

Instructions

Get summarised metadata for a single file / item: name, type, size, version number, dates. Much smaller than the raw JSON:API response. Use for quick file lookups when you already have the item_id from a folder listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID – starts with 'b.'.
item_idYesItem (lineage) URN – starts with 'urn:'.

Implementation Reference

  • The handler logic for 'aps_get_item_details' which validates inputs and calls 'apsDmRequest' and 'summarizeItem'.
    // ── aps_get_item_details ─────────────────────────────────────
    if (name === "aps_get_item_details") {
      const projectId = args.project_id as string;
      const itemId = args.item_id as string;
      const e1 = validateProjectId(projectId);
      if (e1) return fail(e1);
      const e2 = validateItemId(itemId);
      if (e2) return fail(e2);
    
      const t = await token();
      const raw = await apsDmRequest(
        "GET",
        `data/v1/projects/${projectId}/items/${encodeURIComponent(itemId)}`,
        t,
      );
      return json(summarizeItem(raw, { projectId }));
    }
Behavior4/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 effectively describes key traits: it's a read-only operation ('Get'), returns summarized metadata (not raw data), and is optimized for quick lookups. However, it doesn't mention potential errors, authentication needs, or rate limits, which are gaps for a tool with no annotations.

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 front-loaded with the core purpose in the first sentence, followed by usage guidance. Both sentences earn their place by providing essential context without redundancy. It's appropriately sized for a simple lookup tool.

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?

Given the tool's low complexity (2 required parameters, no output schema, no annotations), the description is mostly complete. It covers purpose, usage, and behavioral context well. However, without annotations or output schema, it could benefit from mentioning error cases or response format, though not critical for this simple tool.

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?

Schema description coverage is 100%, so the schema already documents both parameters ('project_id' and 'item_id') with their formats. The description adds no additional parameter semantics beyond implying 'item_id' comes from 'a folder listing', which is minimal value. Baseline 3 is appropriate when the schema does the heavy lifting.

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 specific action ('Get summarised metadata'), resource ('single file / item'), and scope ('name, type, size, version number, dates'). It distinguishes itself from siblings by mentioning it's 'Much smaller than the raw JSON:API response' and contrasts with 'aps_get_folder_contents' and 'aps_get_folder_tree' by focusing on single items rather than listings.

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?

The description explicitly provides when to use this tool ('for quick file lookups when you already have the item_id from a folder listing') and implies when not to use it (when you need raw JSON:API responses or don't have the item_id). It differentiates from siblings like 'aps_get_folder_contents' by specifying it's for single items after obtaining IDs from listings.

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/EverseDevelopment/ACC.MCP'

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