Skip to main content
Glama

ai_modeling_gallery_like

Marks a Studio gallery model as liked by ID, helping agents track and revisit generated 3D assets during workflows.

Instructions

Like a model in the Studio gallery.

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": "ai_modeling_gallery_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation. The description adds nothing beyond that: no idempotency behavior, no auth/account prerequisites, no note about whether liking an already-liked model errors or is a no-op, and no indication of what is returned.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than conciseness: the one sentence carries no actionable content. Nothing is front-loaded because there is nothing substantive to front-load.

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?

For a mutating action tool with no output schema and no parameter documentation, the description should carry the burden and does not. Key facts an agent needs to call it correctly — what 'id' refers to and how to undo or re-invoke — are absent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the single required 'id' parameter, but it does not. The pattern constraint and max length are visible in the schema, yet nothing states that 'id' identifies a gallery model rather than, say, a user or comment.

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 sentence restates the tool name almost verbatim: 'Like a model in the Studio gallery' adds only the notion of a gallery, not a distinct verb+resource scope. An agent still cannot tell from the description whether this is a toggle, a one-way action, or how it relates to sibling ai_modeling_gallery_unlike.

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

Usage Guidelines2/5

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

No when-to-use guidance is given, and no alternative or precondition is named. The existence of a sibling un-like tool makes the missing guidance material: an agent cannot infer from the text whether calling this twice is safe or whether it should check current state first.

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