Skip to main content
Glama

mu

by mu.micro

Edit apps

apps_edit

Edit an app you own — its name, description, tags, icon, HTML or price. Fields left out keep their value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlNoNew HTML, up to 256KB. Left alone if omitted
iconNoNew SVG icon. Left alone if omitted
nameNoNew name. Left alone if omitted
slugYesThe app's URL slug, e.g. pomodoro-timer
tagsNoNew comma-separated tags. Left alone if omitted
priceNoCredits charged per use, 0 for free, up to 1000
descriptionNoNew description. Left alone if omitted

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"New description"New value: +"New description. Left alone if omitted"
    • changedInput schema / properties / html / description
      Previous value: -"New HTML content (max 256KB)"New value: +"New HTML, up to 256KB. Left alone if omitted"
    • changedInput schema / properties / icon / description
      Previous value: -"New SVG icon"New value: +"New SVG icon. Left alone if omitted"
    • changedInput schema / properties / name / description
      Previous value: -"New app name"New value: +"New name. Left alone if omitted"
    • changedInput schema / properties / price / description
      Previous value: -"Credits charged per use (0 = free, max 1000)"New value: +"Credits charged per use, 0 for free, up to 1000"
    • changedInput schema / properties / slug / description
      Previous value: -"The app's URL slug (e.g. pomodoro-timer)"New value: +"The app's URL slug, e.g. pomodoro-timer"
    • changedInput schema / properties / tags / description
      Previous value: -"New comma-separated tags"New value: +"New comma-separated tags. Left alone if omitted"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With annotations containing only the title, the description adds crucial transparency by stating 'Fields left out keep their value', revealing partial-update semantics. This is a key behavioral trait that the agent needs to know for safe invocation.

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, focused sentence that front-loads the core action and ownership requirement, then lists the editable fields, and ends with the critical merge behavior. Every phrase earns its place.

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?

For an edit tool with 7 parameters, no output schema, and minimal annotations, the description covers the essential behavior (partial update) and scope (owned apps). Minor gaps remain about error handling or required permissions, but it is complete enough for a straightforward mutation.

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 lists the fields but does not add meaning beyond the schema's per-parameter descriptions like 'New name. Left alone if omitted.'

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 verb 'Edit' and the resource 'an app you own', and enumerates the editable fields (name, description, tags, icon, HTML, price). This specific wording distinguishes it from siblings like apps_create, apps_read, and apps_fork.

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?

It provides a clear context (must own the app) but does not explicitly mention when not to use or direct to alternatives such as apps_create for new apps. The usage is implied rather than stated.

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

All mu 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.6/5.0
Disambiguation5/5

Every tool is prefixed with a clear domain (e.g., apps_, blog_, transit_), and the suffix identifies a distinct action or resource. Overlapping tools like archive_search and news_search are explicitly differentiated in their descriptions.

Naming Consistency4/5

All tools consistently use a domain_prefix_suffix pattern, but the suffix is sometimes a verb (create, list, search) and sometimes a noun (inbox, status, address). This minor mixing prevents a perfect score but remains predictable and readable.

Tool Count2/5

With 113 tools, the count is far beyond the typical well-scoped range, even for a broad personal assistant. While each tool is distinct and serves a purpose, the sheer number is overwhelming and could be better organized into separate domain-specific servers.

Completeness4/5

Each domain has near-complete lifecycle coverage, including CRUD and search where relevant, with only minor gaps such as missing apps_delete or events_update. The wide range of covered domains itself demonstrates strong completeness for a general assistant.

Resources