Skip to main content
Glama

Dynamoi

by io.github.getDynamoi

Get Smart Link

dynamoi_get_smart_link
Read-only

Use this when the user wants full details for one free Smart Link, including release, Spotify URL, public play.dynamoi.com URL, current status, theme source, and next actions. Set includeAnalytics=true for visit/click analytics and includeArtistSettings=true for artist-level theme/pixel settings. In the final answer, lead with the public URL and do not expose internal IDs unless asked.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNo
artistIdNo
dateRangeNo
playLinkIdNo
spotifyUrlNo
granularityNo
includeAnalyticsNo
includeBreakdownsNo
includeArtistSettingsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
kindNo
statusYes
messageNo

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail about response presentation (lead with public URL, avoid internal IDs) and optional analytics/theme flags, but does not disclose behavior for ambiguous invocations such as no identifier or conflicting identifiers.

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?

Three focused sentences with no filler; the primary purpose is front-loaded, optional flags are grouped, and the response formatting rule is a single clear instruction. Every sentence earns its place.

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 9-parameter tool with no schema descriptions and no required parameters, the description leaves a critical gap: how the agent should identify the target Smart Link (via playLinkId, spotifyUrl, aristsId, or some other route) and what dateRange/granularity/format control. The presence of an output schema helps, but not enough to make the tool safely invocable.

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 compensate for the heavily undocumented parameters. It only explains includeAnalytics and includeArtistSettings, leaving format, artistId, dateRange, playLinkId, spotifyUrl, granularity, and includeBreakdowns unexplained.

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 names a specific verb and resource ('full details for one free Smart Link') and enumerates the returned content: release, Spotify URL, public URL, status, theme source, and next actions. This clearly distinguishes the tool from sibling list/create/update tools.

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 opening 'Use this when the user wants full details for one free Smart Link' gives clear selection context, and 'one' differentiates it from list-oriented siblings. However, it does not explicitly mention alternatives or state when not to use this tool.

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

All Dynamoi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools are cleanly separated by resource and action, and close pairs like account overview vs platform status and singular vs catalog smart-link creation are explicitly disambiguated. The main ambiguity is dynamoi_search versus the connector search tool, which both search the same entities and are distinguished only by chat vs deep-research context.

Naming Consistency4/5

The set overwhelmingly follows a consistent dynamoi_<verb>_<object> snake_case pattern, with predictable get/list/create/update verbs. The unprefixed fetch and search connector tools are a visible but small deviation from that convention.

Tool Count3/5

Seventeen tools is slightly heavy for the server's scope, especially since search/fetch partly duplicate dynamoi_search and the campaign domain is primarily read-only. The smart-link, artist, and distribution clusters each justify their tools, so it is not excessively bloated.

Completeness3/5

Smart links have create/list/get/update coverage and distribution has apply/status, but campaigns are only readable with no create/update/launch tool, despite get_campaign referencing campaign mutations. Platform connections also have status checks but no connect actions, leaving notable workflow gaps.

Resources