Utilia Agent Media and Solana Tools
Server Details
Paid audio/PDF transforms plus live Solana priority fees and preflight diagnostics.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- mohamedkuch/utilia-solana-agent
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
6 toolsnormalize_audioNormalize Audio LoudnessARead-onlyIdempotentInspect
Normalize audio to a bounded 128 kbps MP3 and return base64 output plus loudness measurements. Costs $0.01.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| maxSeconds | No | ||
| targetLufs | No | ||
| audioBase64 | No |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, idempotentHint, and openWorldHint. The description adds cost ($0.01) and output format details, which go beyond the annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences, no redundancy, and directly conveys the core purpose and a key behavioral detail (cost).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given four parameters with no schema descriptions and no output schema, the description is insufficient. It does not explain how to provide input (url vs base64), what maxSeconds or targetLufs mean, or what the output exactly contains beyond 'base64 output plus loudness measurements'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description provides no information about individual parameters (url, maxSeconds, targetLufs, audioBase64). With 0% schema description coverage, the tool fully relies on the description to explain parameters, which it fails to do.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Normalize audio'), the output ('bounded 128 kbps MP3' and 'loudness measurements'), and the result format ('base64'). This distinguishes it from sibling tools which handle PDF or Solana operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for audio loudness normalization, but it does not explicitly state when to use it over alternatives, nor does it mention exclusions or prerequisites. Usage guidance is minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
pdf_to_markdownConvert PDF to MarkdownRead-onlyIdempotentInspect
Extract a PDF into page-delimited Markdown with metadata and a source digest. Costs $0.0025.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| title | No | ||
| maxPages | No | ||
| pdfBase64 | No |
solana_priority_feesGet Live Solana Priority Fee BidRead-onlyIdempotentInspect
Get timestamped network-wide or account-localized priority-fee quantiles before choosing a compute-unit price. Suitable for recurring bot polling. Costs $0.002.
| Name | Required | Description | Default |
|---|---|---|---|
| accounts | No |
solana_token_analysisAnalyze Solana TokenRead-onlyIdempotentInspect
Analyze a Solana mint and holder risks. Costs $0.006.
| Name | Required | Description | Default |
|---|---|---|---|
| mint | Yes |
solana_transaction_analysisAnalyze Solana TransactionRead-onlyIdempotentInspect
Explain a confirmed Solana transaction and classify failures. Costs $0.004.
| Name | Required | Description | Default |
|---|---|---|---|
| signature | Yes |
solana_transaction_simulateSimulate Solana TransactionRead-onlyIdempotentInspect
Simulate a Solana transaction and classify failures. Costs $0.008.
| Name | Required | Description | Default |
|---|---|---|---|
| encoding | No | base64 | |
| transaction | Yes | ||
| accountAddresses | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!