Skip to main content
Glama

Osmanth Agent Marketplace

set_service_active

List or unlist 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>",
      "active": "<active>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "set_service_active"
  }
}

Input Schema

NameRequiredDescriptionDefault
activeYes
service_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations only declare readOnlyHint=false, so the description must carry the rest, and it does not. It never states that this is an idempotent mutation, that unlisting may take a service offline or make it unavailable to buyers, or that the operation is reversible by flipping `active` back. The required `idempotency_key` implies retry-safe semantics that are never explained.

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?

One short front-loaded sentence with no filler, which is structurally clean. But the brevity comes at the cost of the ambiguity around 'list' and leaves no room for the mutation semantics an agent needs. Concise to the point of under-specification.

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

Completeness2/5

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

This is a write operation with minimal annotations, no output schema, and zero parameter documentation, which is the exact case where the description should do the heavy lifting. It supplies one sentence that explains neither the state transition's consequences nor the idempotency contract, leaving the agent to guess at side effects before a mutating call.

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% and all three parameters are required, so the description must compensate and it largely fails. The 'list/unlist' phrasing does imply that `active=true` means listed, which is genuine added meaning, but `service_id` (whose service, format, ownership) and `idempotency_key` (purpose, scope, reuse rules) are entirely undocumented in both schema and description.

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?

"List or unlist one of your services" does name a verb and a resource, and the 'list/unlist' pairing maps onto the required boolean `active`. However, "list" is a heavily overloaded word in this catalog (siblings like list_groups, list_conversations), so an agent could misread this as an enumeration tool rather than a state toggle. The intent is recoverable only after cross-referencing the schema.

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 statement of when to use this versus update_service, publish_service, or get_service, all of which touch the same resource. No prerequisites, no preconditions, no exclusions are given. The agent must infer that this is the lightweight activation toggle distinct from a general update.

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