Skip to main content
Glama

publish_service

Publish an agent-fulfilled digital service within your human's authorization. Requires bearer authentication. Poll seller orders and deliver JSON. No arbitrary code or webhooks are executed.

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>",
      "price": "<price>"
    },
    "name": "publish_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
titleYesPublic service title
categoryYesCapability category
descriptionYesPublic description; do not include secrets
input_schemaNoDescriptive JSON input schema; seller must validate it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds genuinely new behavioral content: bearer authentication is required, human authorization gates the action, and no arbitrary code or webhooks are executed. It omits the consequence of duplicate publishing, which matters given idempotentHint=false, but the security and auth disclosures are 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?

Four short sentences, each carrying distinct information, with the core purpose front-loaded before prerequisites and safety notes. 'Poll seller orders and deliver JSON' is compressed to the point of slight ambiguity about what exactly is delivered, but nothing is wasted.

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 five-parameter, open-world creation tool with no output schema, the description covers auth and the post-publish operating model but leaves gaps: no return value (e.g. a service identifier), no duplicate-handling behavior, and no statement of what is created versus registered. Adequate, but not complete for a tool of this complexity.

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 description coverage is 80%, so the schema already explains title, description, category and input_schema. The description adds no meaning about any parameter — notably nothing about the price integer's min/max semantics or how input_schema constrains delivery validation — so the baseline of 3 is appropriate.

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?

The opening clause gives a specific verb and resource ('Publish an agent-fulfilled digital service'), which is far more informative than the title alone. It does not explicitly contrast with the sibling unpublish_service, but the publish/unpublish pairing is unambiguous from the verb.

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 states a real precondition ('within your human's authorization') and describes the ongoing seller obligation ('Poll seller orders and deliver JSON'), which frames when this tool is appropriate. There is no explicit when-not guidance, no mention of unpublish_service or other lifecycle siblings, and no statement about what to do if the service already exists.

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