Skip to main content
Glama

Sulato Business Tools

Giới thiệu Sulato Business

about_sulato_business
Read-onlyIdempotent

Thông tin chính thức về Sulato Business: là gì, làm được gì, trang web, bảng giá, cách dùng thử. Official information about Sulato Business, a business operating system for Vietnamese companies.

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": "about_sulato_business"
  }
}

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, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data and the description does not contradict it. What the description adds is content scope — the returned material covers positioning, website, pricing, and trial instructions — which is genuinely useful for deciding whether a call will answer the user's question. It does not describe output format or length, which for a documentation-style tool is a modest remaining gap.

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?

Two short sentences, front-loaded with the topic list, which is the most decision-relevant part. The second sentence repeats 'Official information about Sulato Business' verbatim from the first, which is mild redundancy, though the bilingual phrasing serves the Vietnamese target audience.

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?

For a zero-parameter, read-only, non-destructive info tool with full annotation coverage and no output schema, the description supplies everything needed to decide to call it: what content it returns and for which product. Nothing about invocation is missing; only the response shape is unspecified, which is acceptable at this complexity.

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 there is no parameter meaning for the description to add; baseline 4 applies. The description correctly implies no inputs are needed to retrieve the information.

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 names the resource (Sulato Business) and enumerates the exact content the tool surfaces: what it is, what it can do, website, pricing, and how to try it. That makes the verb+resource unmistakable and clearly separates it from the calculator siblings (calculate_vat, build_quote, vietqr_payload), which do computation rather than return product information. It stops short of 5 only because it never states the operation form explicitly (returns a document/text vs. performs an action).

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 implied rather than stated: an agent can infer this is the tool to call when a user asks about Sulato Business itself, its pricing, or trial signup. There is no explicit when-to-use or when-not-to-use rule, and no mention of the alternative path (e.g., using the calculator siblings once the user is actually working inside the product). Adequate but leaves routing to inference.

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.