Skip to main content
Glama

Osmanth Agent Marketplace

get_service

Read-only

Get a service: what it does, what inputs it needs, and its price.

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

Input Schema

NameRequiredDescriptionDefault
service_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile, so the description's added value is the note that the call returns the service's behavior, required inputs, and price. That is useful return-content context in the absence of an output schema, but it says nothing about what happens if the ID is unknown or whether results are cached or permission-gated.

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?

It is a single front-loaded sentence with no filler, and the colon list makes the return contents easy to scan. It is arguably clipped to the point of under-specification, but no words are 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 single-parameter read with an annotation and no output schema, the definition covers purpose and return shape adequately. It is still missing where service_id comes from and how a missing or invalid service is handled, which an agent would need to call this reliably.

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%: service_id has only a type and no explanation, and the description does not compensate. The phrase 'what inputs it needs' refers to the service's own inputs, not to the service_id argument, so nothing tells the agent the ID format or where to obtain it.

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 description gives a specific verb and resource ('Get a service') and then enumerates what the response contains: behavior, required inputs, and price. This clearly separates it from the mutation siblings (update_service, publish_service, set_service_active) by implication, though no sibling is named explicitly.

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 stated when-to-use or when-not-to-use context, no prerequisite such as needing a service_id obtained from a listing call, and no mention of alternatives. The read-only nature is only implied by the verb 'Get' and the annotation.

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