Skip to main content
Glama

GrowVib: Social Media Growth

get_service

Read-onlyIdempotent

Look up ONE service you already have the id for. No id yet? Find one with search_catalog. Want a single option chosen for a quantity rather than all of them? Use recommend_service. Returns the service's full detail, including ALL of its plan options (id, name, price per 1000, min/max quantity, quality tier, typed axes such as country or watch length, listed delivery speed and start window, and the recommended flag), so you can present the available plans and quantity range to the user, then pass the chosen service_option_id to get_quote and create_paid_order (this endpoint lists it while the accountless x402 payment channel is on), or create_checkout when a person will pay in their own wallet instead (listed while checkout sessions are on).

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_idYesThe service id from search_catalog. The catalog slug (telegram-members) is accepted in place of the id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / service_id / description
      Previous value: -"The service id from search_catalog."New value: +"The service id from search_catalog. The catalog slug (telegram-members) is accepted in place of the id"
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes well beyond them: it enumerates exactly what the response contains (all plan options with id, name, price per 1000, min/max quantity, quality tier, typed axes, delivery speed, start window, recommended flag). It also discloses conditional availability of downstream endpoints ('while the accountless x402 payment channel is on', 'while checkout sessions are on'), which no annotation conveys.

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?

The routing guidance is front-loaded before the return-value detail, and nothing is redundant. However, the second sentence is a single very long clause stack with two parenthetical availability caveats, which is dense enough to be slightly harder to parse than necessary.

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

Completeness5/5

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

With no output schema, the description carries the full burden of describing the return payload and does so field by field, plus the quantity-range interpretation and the downstream handoff. For a single-parameter read tool this leaves nothing an agent needs in order to call it and use the result correctly.

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 coverage is 100% for the single parameter and the schema itself documents provenance ('The service id from search_catalog') and the slug fallback. The description restates the id provenance but adds no new format, syntax, or edge-case detail beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

Opens with a specific verb and resource plus an explicit cardinality constraint ('Look up ONE service'), which immediately separates it from list/search-style siblings. It also names both the prerequisite state ('you already have the id for') and the two siblings an agent might otherwise confuse it with.

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

Usage Guidelines5/5

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

Gives explicit branching guidance: no id yet -> search_catalog; want a single chosen option for a quantity -> recommend_service. It then continues the workflow by directing the returned service_option_id to get_quote/create_paid_order or create_checkout, so the agent knows both when to call this and what to do next.

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