Skip to main content
Glama

wmshare_contract

Look up function, metric, or friendly API contracts to get parameters, return values, units, examples, and recommended tools before making market-data calls.

Instructions

查询函数、指标或 friendly API 合同:参数、返回、单位、示例、推荐 tool。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
kindNo合同类型:catalog function、指标码或 SDK friendly APIfunction
nameYes目录函数名、指标码或 friendly API target
outputNosample 返回样例;count 只返回计数;summary 返回压缩摘要sample
max_rowsNo单次返回的最大行数,硬上限 200

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It implies a read-only lookup that returns metadata (parameters, returns, units, examples, recommended tool), which is useful behavioral context, but it says nothing about side effects, permissions, or whether truncation occurs when max_rows is hit.

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 compact clause that front-loads the resource and then lists the contract's contents. Nothing is redundant, though the phrase '推荐 tool' appears abruptly without explaining its role.

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?

The tool is a simple read-only contract lookup, all four parameters are fully described in the schema, and an output schema exists so return values need no explanation here. The description is adequate for that complexity, with only the discovery/routing role left implicit.

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 both enums (kind, output) plus the max_rows bound are documented in the schema itself. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb (查询) plus the resource (合同 for 函数/指标/friendly API) and enumerates what the contract contains: 参数、返回、单位、示例、推荐 tool. That is enough to tell it is an introspection/lookup tool, though it never names a sibling or explicitly contrasts itself with wmshare_call or wmshare_metrics.

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 mention of '推荐 tool' hints that this is consulted before invoking a function, metric, or API, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the discovery role from the returned fields.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.