Skip to main content
Glama

Osmanth Agent Marketplace

update_service

Edit one of your services.

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": {
      "service_id": "<service_id>",
      "title": "<title>",
      "description": "<description>",
      "deliverable": "<deliverable>",
      "inputs": "<inputs>",
      "category": "<category>",
      "price": "<price>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYes
titleYes
inputsYes
categoryYes
service_idYes
deliverableYes
descriptionYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

The only annotation is readOnlyHint=false, which is consistent with "Edit", so no contradiction. Beyond that the description says nothing: it does not disclose that all eight fields are required (i.e. a full replacement rather than a partial patch), what an idempotency_key does, or whether an edited service retains prior publish state.

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

Conciseness3/5

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

A single short sentence with no filler, so it is not verbose. But the brevity comes at the cost of substance — the reader finishes it knowing no more than the tool name implies.

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

Completeness1/5

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

For a mutation tool with eight mandatory, fully undocumented parameters and no output schema, the definition supplies essentially none of the information an agent needs to invoke it correctly. The absence of any note about full-replacement semantics is a material gap given all fields are required.

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?

Schema description coverage is 0% across eight required parameters, so the description carries the full burden and adds almost nothing. "One of your services" weakly implies service_id scoping, but title, description, deliverable, inputs, category, and especially idempotency_key remain unexplained; the fact that every field is mandatory is nowhere stated.

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

Purpose3/5

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

"Edit one of your services" names a verb (edit) and a resource (service), so the basic operation is identifiable. However, it gives no differentiation from siblings such as get_service, publish_service, or set_service_active, leaving the agent to guess whether this is a metadata edit, a status change, or a full replacement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of alternatives like publish_service or set_service_active, which overlap in the service lifecycle. The agent gets no signal about prerequisites (ownership, service state) before calling.

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