Skip to main content
Glama

Read how to publish a Hosted App

describe_hosted_app_publishing
Read-onlyIdempotent

Reference for publish_app_version, returned on demand: how an app calls Requests over HTTP (execute contract, error codes, stream_status completeness), confirmation screens and pending actions, data-backed storage, Request recording (strict_recording, calls_without_grant), staging precedence and retries, in-file edits and their limits, and each long parameter in full. No arguments. Read it before writing an app that calls Requests, and when a publish_app_version refusal names it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the reference is 'returned on demand' and takes 'No arguments', making clear this is a static fetch rather than an operational call; it stops short of indicating document size or whether the content is versioned alongside the app.

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?

Front-loaded with what the reference is, then a dense but purposeful topic inventory, then the calling instruction. Every clause is a scannable content marker that helps an agent decide whether to fetch it; no filler sentences.

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

Completeness5/5

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

For a zero-argument, read-only documentation tool with no output schema, the description does the full job: it says what the document contains, that it takes no input, and the exact conditions under which to fetch it. Nothing an agent needs in order to call it correctly is missing.

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?

Zero parameters, so the schema has nothing to explain and baseline is 4. The description correctly and explicitly notes 'No arguments', removing any doubt about calling it empty.

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 — a reference document for publish_app_version — and enumerates exactly what it covers (HTTP Requests contract, error codes, stream_status completeness, confirmation screens, storage, recording flags, staging precedence, parameter documentation). It is unmistakably a documentation-lookup tool and is clearly distinguished from publish_app_version itself.

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?

Gives two explicit triggers: read it before writing an app that calls Requests, and when a publish_app_version refusal names it. That is strong when-to-use guidance, though it does not mention when-not to call it or how it relates to documentation-adjacent siblings like describe_application or read_app_file.

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