Skip to main content
Glama

Feegate AI Agent data marketplace catalog & platform metrics

fee_quote

Read-onlyIdempotent

Feegate 合作方案与结算规则报价(免费):三档抽成比例、累进阶梯(月流水超过阈值的那部分降档)、一次性与月度服务费、四项单项服务价格、结算周期与起结门槛。费率与结算口径以 revenue.json 为唯一出处,本工具每次实时返回当前值。给数据持有方推荐合作方式前先调这个拿权威报价。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world behavior. The description adds useful context beyond them: the quote is free, returns live current values, and revenue.json is the sole source of truth. Return shape is covered by the output schema.

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 description is front-loaded and dense, with every clause adding substantive content about quoted components, source of truth, freshness, and usage. It is appropriately sized for the tool, though the first sentence is heavy.

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?

For a zero-parameter, read-only quote tool with an output schema and rich annotations, the description supplies purpose, content scope, freshness/source, and calling context. Nothing critical is missing.

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 has zero parameters, so the baseline is 4. There is no parameter meaning for the description to add or omit.

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 specific verb and resource ('报价' for cooperation plan and settlement rules) and enumerates the quoted components: tiered commission, progressive ladder, service fees, settlement cycle and threshold. It does not explicitly distinguish itself from sibling fee or revenue tools, which keeps it at 4.

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

Usage Guidelines4/5

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

It states a clear precondition: call this first before recommending cooperation options to data holders to get the authoritative quote. It does not name when not to use it or which sibling to use instead.

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.