Skip to main content
Glama

了解万宝屋

get_site_info
Read-onlyIdempotent

读取万宝屋的平台介绍、注册准入、万宝币 WBC 规则、常见问题和官方入口。

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_site_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds the topical scope but says nothing about caching, freshness, or what the payload looks like; with no output schema, that gap matters more.

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 front-loaded sentence listing the covered topics, with no filler or repetition. It is appropriately sized for a no-parameter static-info tool.

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 lookup with rich annotations and no output schema, enumerating the content areas is close to sufficient. What is missing is any hint about the response structure (sections, language, or format) so an agent knows what to expect when it calls.

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?

The tool takes zero parameters, which normally sets a baseline of 4, but the description offers nothing about the return shape even though there is no output schema. The parameter dimension itself is unproblematic; the missing return detail is better counted under completeness.

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 uses a concrete verb (读取) plus an enumerated resource set: platform introduction, registration eligibility, WBC coin rules, FAQ and official entry points. This goes beyond the title 了解万宝屋 and makes the tool's scope recognizable, though it does not explicitly contrast itself with get_request_guide.

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?

The content list implies when the tool is useful (when an agent needs platform background, onboarding rules or coin policy), but there is no explicit when-to-use statement, no prerequisites, and no mention of the sibling get_request_guide as an alternative.

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