Skip to main content
Glama

Service information

get_service_info
Read-only

What the service translates, what files it accepts, limits (file size, pages, words, requests per hour), prices (yen, tax included), delivery times and how ordering and payment work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_service_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-domain read. The description adds useful scope detail about what categories of information are returned, but says nothing about the freshness of the limits/prices, the format of the response, or whether any auth is needed. With annotations covering the safety profile, this is a moderate contribution.

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?

A single tight sentence with no filler, and the most important framing (what the service translates) comes first. It is grammatically a fragment without a leading verb, which slightly weakens front-loading, but there is no waste.

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

Completeness4/5

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

With no parameters and no output schema, the description's job is to convey what comes back, and it does so with a concrete enumeration of fields (file size, pages, words, requests/hour, yen prices tax included, delivery times). Only the response structure and currency/locale caveats beyond yen are left unstated, which is minor for a parameterless info tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4. The description does not need to add parameter meaning, and its content list instead usefully sets expectations for the return payload.

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 enumerates exactly what content the tool surfaces (translation scope, accepted files, limits, prices, delivery times, ordering/payment flow), which makes the resource unambiguous and clearly distinct from siblings like quote_document or create_order. It lacks an explicit verb ('returns'/'gets'), reading as a noun phrase, but the name plus content list is enough for an agent to identify it.

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?

Usage is only implied: the enumerated limits, prices and ordering/payment details suggest this is the reference lookup to call before quoting or ordering. There is no explicit 'call this when...' statement, no exclusion of alternatives, and no mention of how it relates to quote_document or create_order.

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