Skip to main content
Glama
Sign In
@callirra/mcp

@callirra/mcp

Official
by callirra-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_asset

Read-onlyIdempotent

Retrieve a single owned asset by ID and refresh its signed media URL so agents can access current media links.

Instructions

Read one owned asset and refresh its signed media URL.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.1

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description is not carrying the full safety burden. It adds useful context that the asset must be owned and that the signed media URL is refreshed, though it does not mention authentication requirements, rate limits, or whether the refresh has persistent effects.

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 definition is a single front-loaded sentence with no redundant or wasted wording. It communicates the core operation and side behavior directly.

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 one-parameter read tool with rich annotations, the description is minimally adequate. However, with no output schema, it could better explain the returned asset data or signed URL, and it leaves the id parameter undocumented.

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?

There is one required parameter, id, and schema description coverage is 0%, so the description should compensate but does not explain what the id represents, its format, or where to obtain it. "Read one owned asset" only weakly implies that an asset identifier is needed.

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

Purpose4/5

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

The description states a clear verb and resource ("Read one owned asset") plus a specific behavior ("refresh its signed media URL"). It is distinguishable from collection-level or write operations, but it does not explicitly name sibling alternatives such as list_assets or download_asset.

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?

Usage is implied: fetch a single owned asset by id while obtaining a fresh signed URL. However, there is no explicit guidance on when to use this instead of list_assets, download_asset, or update_asset, and no stated prerequisites or exclusions.

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