Skip to main content
Glama

ai_modeling_project_related

Read-only

Find gallery models related to a specific project so you can review, select, or reuse assets linked to that project.

Instructions

Find gallery models related to a project.

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": {
      "project_id": "<project_id>"
    },
    "name": "ai_modeling_project_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
localeNoen
project_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that: it does not explain what makes a model "related", whether results are ranked or paginated, why openWorld access is needed, or what the locale parameter affects.

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?

A single front-loaded sentence with no filler or redundancy. It is terse rather than bloated; the weakness is under-specification, not verbosity.

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?

With 0% parameter documentation, no output schema, and open-world behavior, the definition leaves too much unexplained for correct invocation. An agent cannot tell what the return set looks like or how to control it via limit/locale.

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% across three parameters, and the description compensates for none of them. It weakly implies project_id via "related to a project", but never mentions limit (default 10, max 100) or locale (default en), nor the accepted project_id format.

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

Purpose3/5

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

The description supplies a verb+resource pair ("Find gallery models related to a project"), but "gallery models" is unexplained jargon and "related" is undefined (same project? same author? same tags?). It does not differentiate this from siblings that also retrieve project-adjacent resources such as ai_modeling_assets_list or ai_modeling_canvas_asset_get.

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?

There is no statement of when to call this versus the many other project/model retrieval siblings, and no preconditions or exclusions. The agent must infer the use case entirely from the tool name.

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