Skip to main content
Glama
Sign In
3D-MCP

3D-MCP

by team-plask
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

getMetadata

Extract specific metadata or full metadata details from an entity by providing its identifier and optional key. Designed for integration with 3D-MCP, enabling structured access to entity data in digital content workflows.

Instructions

Get metadata from an entity

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "getMetadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntity identifier
keyNoSpecific metadata key to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior1/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 of behavioral disclosure. It only states the action ('Get metadata') without describing permissions, side effects, rate limits, or return format. This is inadequate for a tool that likely interacts with a 3D modeling system, as seen in sibling tools.

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 a single, efficient sentence with no wasted words. It is front-loaded and appropriately sized for the tool's apparent simplicity, though this conciseness comes at the cost of detail.

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?

Given the lack of annotations and output schema, and the description's minimal content, this is incomplete. It does not address behavioral aspects, usage context, or return values, which are critical for a tool in a complex 3D modeling environment with many sibling tools.

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%, with clear parameter descriptions in the input schema. The description adds no additional meaning beyond what the schema provides, such as examples or constraints. Baseline score of 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get metadata from an entity' restates the tool name 'getMetadata' without adding specificity. It does not clarify what type of entity (e.g., 3D model component, scene object) or what metadata format is involved, nor does it distinguish from sibling tools like 'getProperty' or 'query' that might retrieve similar information. This is a tautology with minimal added value.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusions, and it fails to differentiate from sibling tools such as 'getProperty' or 'setMetadata'. This leaves the agent without usage direction.

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

Deploy Server

Other Tools

Related Tools