Skip to main content
Glama

Show with MONETEKA photos

render_moneteka_view
Read-only

Show coins with MONETEKA's own photos, prices and links, or the account panel. tool names the MONETEKA read tool whose answer is shown (search_coins, get_coin_details, get_catalog_entity, compare_coins, get_related_coins, get_coin_prices, get_my_collection, get_my_wishlist or get_collection_analytics) and the other arguments are that tool's arguments. It changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
toolNoThe MONETEKA tool whose answer to show, e.g. search_coins.
viewNoOptional; taken from the tool.
argumentsNoThe same arguments that tool was called with.
result_refNoInstead of tool and arguments: result_ref as a MONETEKA tool returned it.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, it discloses what actually gets rendered (photos, prices, links, account panel) and the key behavioral contract that the arguments mirror the underlying tool's arguments and nothing is modified. No additional limits, but the tool is a pure view layer with an output schema, so little more is needed.

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?

Two tight sentences: purpose first, then the parameter contract, closing with the safety note. No redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering safety, a full schema, and an output schema, the description supplies everything essential an agent needs to route a read through the view layer. The only soft spot is the loosely described 'account panel' case and no explicit guidance on choosing this over the underlying tool.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description adds real meaning the schema cannot: the enumerated `tool` values are the read tools whose answers are shown, and `arguments` must be the exact arguments that tool was called with. `view` and `result_ref` are left to the schema, which documents them adequately.

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?

States a specific verb and resource ('Show coins with MONETEKA's own photos, prices and links, or the account panel') and explicitly frames it as a renderer of another MONETEKA read tool's answer, which distinguishes it from the data-fetching siblings it names.

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

Usage Guidelines4/5

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

The description makes the usage pattern clear: pick a MONETEKA read tool via `tool` and pass that tool's arguments, so an agent knows this is the display layer rather than a data source. It does not spell out when to prefer this over simply returning the underlying tool's raw output, so it stops short of explicit when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources