General Average for agent fleets

declare_event

Issue a signed GA declaration for a sacrifice event (sacrificed must be an enrolled member; above 20 events/mo an X-PAYMENT header on the MCP request is required)

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": {
      "fleet_id": "<fleet_id>",
      "authority": "<authority>",
      "authority_secret": "<authority_secret>",
      "event_id": "<event_id>",
      "peril": "<peril>",
      "sacrificed": "<sacrificed>",
      "sacrifice_kind": "<sacrifice_kind>",
      "benefited": "<benefited>",
      "metered": "<metered>",
      "claimed_loss_cents": "<claimed_loss_cents>"
    },
    "name": "declare_event"
  }
}

Input Schema

Name	Required	Description	Default
`peril`	Yes
`metered`	Yes
`event_id`	Yes
`fleet_id`	Yes
`authority`	Yes
`benefited`	Yes
`sacrificed`	Yes
`sacrifice_kind`	Yes
`authority_secret`	Yes
`claimed_loss_cents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 29, 2026

addedInput schema / properties / authority
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / authority_secret
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / benefited
```
Added value: +{
+  "type": "array"
+}
```
addedInput schema / properties / claimed_loss_cents
```
Added value: +{
+  "type": "integer"
+}
```
addedInput schema / properties / event_id
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / metered
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / peril
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / sacrifice_kind
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / sacrificed
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / required

Previous value: -[
-  "fleet_id"
-]New value: +[
+  "fleet_id",
+  "authority",
+  "authority_secret",
+  "event_id",
+  "peril",
+  "sacrificed",
+  "sacrifice_kind",
+  "benefited",
+  "metered",
+  "claimed_loss_cents"
+]

First observedOct 22, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two valuable traits beyond the schema: an enrollment validation rule and a metered rate limit with a payment-header requirement. It says nothing about idempotency on event_id, reversibility of an issued/signed declaration, or authentication failure modes, which matter for a signing mutation.

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?

A single front-loaded sentence with the core action first and constraints in parentheses. Nothing is wasted, though the density makes the parenthetical clause easy to skim past.

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?

Placeholder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 10 required parameters including a nested object, yet the description only touches one parameter ('sacrificed') and its enrollment constraint. fleet_id, authority, authority_secret, event_id, peril, sacrifice_kind, benefited, metered, and claimed_loss_cents are left entirely undocumented in both schema and prose.

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?

States a specific verb and artifact: issuing a signed GA declaration for a sacrifice event. That is distinguishable from siblings like settle_event, adjust_event, and list_receipts by verb and output, though the domain jargon ('GA declaration') is not unpacked.

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?

Provides two real preconditions: the sacrificed party must be an enrolled member (implying enroll_fleet must run first) and above 20 events/mo requires an X-PAYMENT header. It never says when to use this versus adjust_event or settle_event, so the routing guidance is implied rather than stated.

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

All General Average for agent fleets 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?