Skip to main content
Glama

publish_capability

Publish a versioned executable capability you have authority to offer. Run a provider worker for this capability; publishing alone does not provision compute. JSON Schema subset is validated server-side.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "description": "<description>",
      "category": "<category>",
      "version": "<version>",
      "price": "<price>",
      "timeout_seconds": "<timeout_seconds>",
      "runtime": "<runtime>",
      "license": "<license>",
      "input_schema": "<input_schema>",
      "output_schema": "<output_schema>"
    },
    "name": "publish_capability"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
titleYesPublic service title
licenseYes
runtimeYes
versionYesImmutable version identifier
categoryYesCapability category
descriptionYesPublic description; do not include secrets
input_schemaYes
output_schemaYes
timeout_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the mutation and open-world profile, and the description adds genuinely new behavior: publishing does not provision compute, a worker must be run separately, and the JSON Schema subset is validated server-side. It does not mention auth requirements, rate limits, or what happens on version conflicts, but the added context is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and immediately followed by the most important operational caveat. No filler, though the schema-validation sentence is somewhat terse and could be folded into the compute caveat.

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

Completeness3/5

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

For a 10-required-parameter mutation with no output schema and low schema coverage, the description covers the critical gotcha (no compute without a worker) but leaves most parameter meaning and the publish/withdraw lifecycle unaddressed. Adequate to avoid a wrong call, not adequate to call it correctly on the first try.

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?

With 10 required parameters and only 40% schema description coverage, the description should carry more weight, yet it only indirectly touches input_schema/output_schema (server-side validation) and version (immutability). Price, timeout_seconds, runtime, license, and category are left entirely to the schema, and the 'execution-only' license enum and runtime choices are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Publish a versioned executable capability') plus an authority qualifier, which is more than a restatement of the name. It does not, however, distinguish itself from the sibling publish_service, so an agent cannot tell from the description alone which of the two to call.

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?

The line 'Run a provider worker for this capability; publishing alone does not provision compute' gives useful context about the follow-up step, but it is a caveat rather than when-to-use guidance. There is no explicit statement of when to choose this over publish_service or the other publish/register siblings.

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