Skip to main content
Glama

Query Oil Price

query_oil_price

查询国内成品油价格(92号/95号/98号汽油、0号柴油)。传入省份名查该省油价,如"山东";不传则返回全国31个省区市油价列表。返回下一轮调价窗口日期。

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

Input Schema

NameRequiredDescriptionDefault
provinceNo省份名称(可选),如 "山东"、"北京"、"广东"。 不传或传空字符串则返回全国各省油价列表。 支持简称(鲁→山东,京→北京)、全称(山东省)。

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / province / description
      Added value: +"省份名称(可选),如 \"山东\"、\"北京\"、\"广东\"。\n      不传或传空字符串则返回全国各省油价列表。\n      支持简称(鲁→山东,京→北京)、全称(山东省)。"
    • removedInput schema / properties / province / title
      Removed value: -"Province"
    • removedInput schema / title
      Removed value: -"query_oil_priceArguments"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description has to carry the full behavioral burden. It does disclose useful return characteristics: the no-parameter call yields a list covering 31 province-level regions, and the response includes the next price-adjustment window date. However, it says nothing about data source, unit and currency (元/升), freshness, or whether the call is a pure read — meaningful gaps for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, each earning its place: scope and covered grades first, then the conditional behavior, then a note on the returned adjustment date. No filler and the primary usage rule is front-loaded.

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 one-optional-parameter read tool with full schema coverage and an output schema, the description covers both invocation modes and hints at the payload. Only minor ambient details, such as unit and data freshness, are absent, and some of that is a reasonable job for the output schema.

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 description coverage is 100%, and the schema already documents the optional province parameter, including support for short forms (鲁→山东) and full names; the description mostly restates this and adds only an example value. The baseline of 3 is appropriate when the schema does the heavy lifting and the description adds marginal meaning.

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?

The description states a specific verb and resource (查询国内成品油价格), enumerates the fuel grades it covers (92/95/98号汽油、0号柴油), and defines the two operating modes: a single province or all 31 provinces. An agent knows exactly what domain of data this tool returns without opening the schema.

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 gives a clear conditional rule: pass a province name to get that province's prices, or omit it to get the nationwide list, with a concrete example ("山东"). There are no sibling tools, so no alternatives need naming; the only gap is that it says nothing about when this tool is unsuitable, such as the data's update cadence.

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.