Skip to main content
Glama

Agentic Endpoints

by com.oliverkiss

Release a claim whose work failed

once_key_release
Idempotent

Free. Surrenders a claimed action_key so a retry can start immediately instead of waiting out the lease. Call this when the work you claimed fails. Refuses if the key was already completed, because releasing it would discard the recorded result and allow the side effect to run twice. This tool is free; no payment is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceYesIsolation scope used when the key was claimed
action_keyYesThe action_key to release
namespace_tokenNoOne-time token issued by the first call that claimed this namespace. Required for every later call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes'released'
action_keyYesThe key that was surrendered

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Discloses a key refusal behavior: releasing an already completed key is refused because it would discard the recorded result and risk running the side effect twice. This goes beyond the annotations by explaining failure semantics and safety rationale. No contradiction with annotations.

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?

Mostly efficient and informative, but the free/no-payment point is stated twice ('Free.' and 'This tool is free; no payment is required.'), wasting a sentence. Otherwise tightly written and front-loaded.

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?

For a moderate-complexity tool with full schema coverage and an output schema, the description covers what the tool does, when to call it, and the important refusal behavior. An agent has enough to invoke it correctly and avoid dangerous misuse.

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%, so parameters are already fully documented. The description adds little param-specific detail, but the baseline of 3 applies because the schema carries the load.

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 ('surrenders'/'release') and resource ('claimed action_key'), with a clear effect: letting a retry start immediately. This distinguishes it from sibling claim/complete operations even though those tools aren't named.

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?

Explicitly says 'Call this when the work you claimed fails' and explains the benefit over waiting out the lease. It does not name an alternative tool for success cases, but the condition is clear enough.

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

All Agentic Endpoints toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool maps to a distinct resource and action: meetings have import/list/search/get, the once-key system has claim/complete/release, vault has store/retrieve/exists/list/delete/rotate_token, and compress/pdf_parse/scrape are separate utilities. No two tools appear to perform the same side effect, so an agent should not struggle to choose among them.

Naming Consistency5/5

Tools use consistent snake_case and mostly follow a domain_verb pattern (meetings_*, once_key_*, vault_*), with standalone verbs like compress, scrape, and pdf_parse for single utilities. The naming is predictable and easy to extend.

Tool Count4/5

At 16 tools the server is just above the ideal 3-15 range, but the count is justified by six distinct capability clusters. Each tool earns its place, and nothing feels redundant.

Completeness4/5

Core lifecycles are covered well: vault has full CRUD plus token rotation, once-key has claim/complete/release, and meetings provide import/search/get/list. Minor gaps include no meeting update/delete and no direct namespace management, but these are workable rather than blocking.

Resources