Skip to main content
Glama
Sign In
ontopoc

ontopoc

by Longado
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

confirm_derived

Saves a reviewed derived metric formula and recomputes its test cases after human approval. Use it to confirm the formula and trial results before persisting.

Instructions

确认一个派生指标（例如 金额 = 单价 × 数量 ×（1 − 折扣））：服务再核一遍公式，存下后重算等它的题。只在人看过公式和试算结果、同意之后调用；derive 用那道题返回的 derive 原样传。

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": {
      "saved_as": "<saved_as>",
      "derive": "<derive>"
    },
    "name": "confirm_derived"
  }
}

Input Schema

NameRequiredDescriptionDefault
deriveYes{type, label, terms}，来自那道题的 derive
saved_asYes运行的保存名，来自 list_runs 或 build_ontology

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses server-side re-validation of the formula, persistence, and recomputation of dependent questions, plus a human-approval precondition. It stops short of describing failure behavior or whether an existing confirmed metric can be overwritten.

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?

Front-loads the confirm action with a compact illustrative formula, then the precondition, then the payload rule. Dense but every clause carries information; the parenthetical example earns its space by disambiguating what a derived metric is.

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 persistence tool with no annotations and no output schema, it covers purpose, side effects, and the human-approval gate adequately. Minor gaps remain around error handling and what the tool returns after saving, but nothing critical to correct invocation 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?

Schema coverage is 100%, so the baseline is 3, but the description adds a meaningful constraint beyond the schema: the derive object must be the one returned by that question, passed unmodified. That guards against an agent reconstructing the formula. The saved_as parameter is left entirely to the schema's own explanation.

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?

Uses a specific verb (确认/confirm) plus a specific resource (派生指标/derived metric), and immediately illustrates with a concrete formula (金额 = 单价 × 数量 ×（1 − 折扣）). It also states the downstream effect (re-verify the formula, save it, recompute dependent questions), so an agent knows exactly what the call accomplishes 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?

Gives an explicit gating precondition: only call after a human has reviewed the formula and trial results and agreed. It also tells the agent how to supply the payload ('pass derive as-is from that question'). No sibling alternative is named or excluded, which keeps it short of a 5.

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

Deploy Server

Other Tools