cogmemai

Agent readability score

Strengths

• Tool names like 'get_market' and 'build_add_liquidity_tx' clearly indicate their purpose.
• Descriptions often mention use cases (e.g., 'for on-chain trading' in 'get_networks').

Weaknesses

• Some parameter requirements are ambiguous (e.g., 'chain_id' in 'get_market_history' is optional but not explicitly stated).
• Multiple transaction-building tools (e.g., 'build_buy_shares_tx' vs. 'build_buy_with_approval_tx') may cause agent confusion.
• Error handling and constraints (e.g., 'only works after resolution' in 'build_claim_winnings_tx') are not consistently documented.

• build_buy_with_approval_tx — Combines two steps but lacks clarity on parameter dependencies
• get_allowance — Does not specify consequences of insufficient allowance
• get_networks — Implies importance for trading but lacks concrete use examples

Verdict

Tools are generally well-named and contextually described, but overlapping transaction tools and inconsistent error documentation risk agent confusion. The 70/100 score reflects clear naming strengths but highlights gaps in parameter clarity and constraint documentation.

9/11/2026, 2:56:59 AM

Event narrative

Server transitioned from 'auth-gated' to 'legacy' era with compliance score rising to 100.

Risk: medium

• 2026-09-10T21:16:35.016Z — era changed from null to 'auth-gated', complianceScore became null · Initial state shows incomplete compliance data during auth-gated era
• 2026-09-11T01:59:45.474Z — era changed from 'auth-gated' to 'legacy', complianceScore rose from null to 100 · Successful transition to legacy era with full compliance achieved

Advice

Monitor compliance score stability in legacy era. Verify if era change was intentional. Investigate why smokeOk remains null in both measurements.