OTP

List scorecard KPIs

list_my_kpis

Read-only

List KPIs (scorecard measurables) on the org chart, filterable by owner, each with its goal and its latest recorded value, the period that value is for, and whether it meets the goal. Use this to see what an agent or human is being measured against, which KPIs are off goal, and to find a KPI's id or exact title before pushing a value with update_kpi. latest_value is null when nothing was recorded recently; meets_goal is null when there is no value or no goal.

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

Input Schema

Name	Required	Description
`include_values`	No	Attach latest_value, latest_period_start and meets_goal. Default true; pass false for the bare list.
`owner_entity_type`	No	Filter by entity type.
`owner_external_id`	No	Filter to one owner's KPIs. E.g. 'AGT_DIRK' for the Dirk agent, 'HUM_DAVIDSTEEL' for David.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine behavioral context by explaining when fields come back null: latest_value is null with nothing recorded recently, meets_goal is null with no value or no goal. It doesn't cover pagination or result size, but the null semantics are the kind of thing an agent would otherwise misread as an error.

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-loaded with what the tool returns, then the use cases, then the null caveat. The middle clause ('each with its goal and its latest recorded value, the period that value is for, and whether it meets the goal') is dense but informative. Minor redundancy between the first two sentences keeps it just short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of describing the return shape and does so precisely: goal, latest value, period, and meets_goal, plus the null conditions. For a three-optional-parameter read tool with full annotation coverage, an agent has everything needed to call it correctly.

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 every parameter, including the include_values default and owner id examples, is already documented there. The description only echoes the owner filter and, indirectly, what include_values controls. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific verb and resource ('List KPIs (scorecard measurables) on the org chart') and immediately qualifies scope with 'filterable by owner'. The name alone is ambiguous next to update_kpi, but the description pins down the read-only listing role and even glosses what a KPI is.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names three use cases: seeing what an agent or human is measured against, finding off-goal KPIs, and looking up a KPI's id or exact title. It also routes the agent to the sibling tool ('before pushing a value with update_kpi'), making the boundary between reading and writing unambiguous.

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

All OTP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?