Gemral Edge

Get Open Corporate Promises

get_open_promises

Retrieve all pending active commitments and upcoming deadlines for a company or category. Sorted by target deadline date to identify upcoming catalysts and delivery checkpoints.

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

Input Schema

Name	Required	Description
`limit`	No
`ticker`	No	Stock ticker, e.g. PLTR
`category`	No	Filter by claim category, e.g. financial, operational, product, technology

Output Schema

Name	Required	Description
`notice`	No	Free-tier upgrade notice; only when results are masked/delayed.
`results`	Yes	Tool result payload (read-only evidence). Shape varies by tool; scoring weights are never exposed.
`history_limit`	No	Present when the license limits history depth: earliest_allowed date, history_days and how many older items were removed.
`deprecated_fields`	No	Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / deprecated_fields

Added value: +{
+  "description": "Present only while a renamed key is still returned next to its replacement: field (old key), replacement (new key, same value), removal (ISO date after which the old key is gone).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description frames the operation as a pure read ('Retrieve all pending...'), but the annotations declare readOnlyHint=false, indicating side effects the description never discloses. destructiveHint=false and openWorldHint=false do reduce safety concerns, but the read framing versus the non-read-only annotation leaves a real transparency gap.

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?

Two sentences with the purpose and scope front-loaded, followed by sort order and use case. Efficient and readable, though the trailing 'catalysts and delivery checkpoints' phrase is slightly promotional for the information it adds.

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

Completeness3/5

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

With an output schema present, return values need no explanation, and the sort order is stated. Still, the description does not clarify what qualifies as 'pending active' versus overdue, nor does it help the agent choose between this and closely related sibling tools, leaving meaningful gaps for a tool in a crowded namespace.

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?

The schema documents ticker and category with examples, and the description echoes the 'company or category' filtering idea. However, the description says nothing about the limit parameter, how truncation works, or what happens if both ticker and category are omitted, which is notable with only 67% schema description coverage.

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?

Uses a specific verb 'Retrieve' and a concrete resource 'pending active commitments and upcoming deadlines,' scoped to 'a company or category.' The sort order is also stated. However, the description does not explicitly distinguish it from close siblings like get_overdue_promises (the likely inverse) or search_management_promises, so a small amount of inference remains.

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?

The phrase 'to identify upcoming catalysts and delivery checkpoints' gives an implied use case, and the sorting rationale helps. But there is no explicit when-to-use / when-not-to-use guidance and no mention of the alternative tools an agent should consider instead, despite at least three related siblings.

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

All Gemral Edge 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.