NomaCMS MCP Server

Official

by NomaCMS

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Asset

get_asset

Retrieve an asset by its UUID or filename. Set by_name to true for filename lookup.

Instructions

Get an asset by its UUID or by filename.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_asset"
  }
}

Input Schema

Name	Required	Description	Default
`by_name`	No	If true, looks up by filename instead of UUID
`identifier`	Yes	Asset UUID or filename

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.1Jul 11, 2026

TDQS

A3.5/5.0

Behavior2/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. It does not disclose read-only nature, error behavior for missing assets, or any prerequisites. Only states what the tool does, not how it behaves beyond that.

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 filler. Every word adds value.

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?

For a simple get tool with 2 parameters and no output schema, the description is minimally adequate. However, it lacks details on return format, error behavior, or confirmation that it is a read-only operation, which would enhance 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?

Schema coverage is 100%, so the baseline is 3. The description adds context that the tool supports two lookup modes (UUID or filename), which aligns with the 'by_name' boolean. However, it does not provide syntax or examples beyond the schema.

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 tool retrieves a single asset by UUID or filename, distinguishing it from list_assets and delete_asset. The verb 'Get' and resource 'asset' are specific.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a single asset by two methods, but does not provide explicit guidance on when to use this tool versus alternatives like list_assets or search endpoints. No exclusions or context for selection.

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