Skip to main content
Glama

机构/大V历史截面评分(PIT)

get_agency_pit
Read-onlyIdempotent

机构/大V历史截面评分(PIT)。查某一天当时的机构/大V分(PIT=只用那天已经知道的数据计算,不会“偷看未来”),适合回测。返回不晚于 as_of_date 的最近一个已发布日期的数据。(每次调用计费 1 次)

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数,默认 50,最大 500
offsetNo分页偏移
agency_idNo只看某个机构/大V(agency_id)
min_scoreNo最低机构/大V分
as_of_dateNo截面日期,默认最新面板日

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / agency_id / description
      Previous value: -"只看某个匿名机构/大V"New value: +"只看某个机构/大V(agency_id)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behavior, so the bar is lower; the definition still adds real value by declaring billing (1 credit per call) and, crucially, the fallback rule — it returns the latest published date not later than as_of_date rather than erroring. That fallback is exactly the behavior an agent cannot infer from structured fields.

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 definition is front-loaded with the purpose, and each parenthetical (PIT definition, billing) earns its place. Mild redundancy from restating the title and repeating the as_of_date idea twice keeps it from a 5.

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 5-parameter read-only tool with full schema coverage and no output schema, this covers the essentials: what is measured, when, and at what cost. The one gap is that it never sketches the returned record (one row per agency with a score), which the absent output schema would otherwise have carried.

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?

Schema coverage is 100%, so baseline is 3; the definition goes beyond the schema by clarifying that as_of_date selects the snapshot date and that returned rows may come from an earlier published date. It does not add anything about agency_id, min_score, limit, or offset, but those are fully described in the schema.

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 definition names a specific verb and resource — the historical point-in-time (PIT) agency/KOL cross-section score — and explains what PIT means (only data known as of that day; no look-ahead). The purpose is clear, but the definition does not contrast with sibling tools such as get_agency_history or get_agency_ranking, leaving the agent to infer which one it wants.

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?

"适合回测" implies a usage context, which is helpful, and the PIT explanation hints at why an agent would pick this tool over a non-PIT history tool. However, it neither excludes any case nor names an alternative, and it never points to list_agency_pit_dates, the obvious companion for discovering valid as_of_date values.

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