Skip to main content
Glama

Estimate FlexCredits / 预估 FlexCredit

estimate_task_cost
Read-onlyIdempotent

Estimate the maximum FlexCredit cost for an uploaded simulation task without initiating its execution.

Instructions

读取已上传任务的最大 FlexCredit 预估,不启动任务。 / Read the maximum FlexCredit estimate for an uploaded task without starting it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask identifier returned by upload_simulation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

注解已提供 readOnlyHint=true、idempotentHint=true 和 destructiveHint=false,覆盖了安全性。描述补充了“最大”预估和“不启动”的行为,但没有进一步说明如异步性、费用影响或副作用,在注解覆盖下该级别是合理的。

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?

描述简短且信息集中,双语版本但内容不冗余。第一句给出了核心行为和限制,结构清晰。虽然双语可能稍显重复,但整体简洁高效。

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?

存在输出模式,因此无需在描述中解释返回值。工具简单,只有一个参数,描述已提供核心行为和安全属性。唯一缺失的是明确的使用时机(如“在启动前需要知道预估”),但整体上对于该简单工具已足够完整。

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?

只有一个参数 task_id,schema 描述为“Task identifier returned by upload_simulation”,覆盖率 100%。描述未在文本中重复参数说明,但 schema 已完全覆盖,因此基线为 3。

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?

描述明确说明了动词“读取”、资源“最大 FlexCredit 预估”和操作对象“已上传任务”,并明确指出“不启动任务”。这清晰地区分了该工具与 start_simulation 等启动类工具,尽管没有直接命名替代工具,但目的明确。

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?

描述说明了用途(读取预估)和关键约束(不启动任务),提供了清晰的使用上下文。虽然没有明确列出替代工具,但“不启动任务”这一否定条件暗示了何时使用(预估)以及何时不使用(启动)。

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