Skip to main content
Glama

Ausca

by com.ausca

Mint a browser CDP connection

ausca_browser_session_connect
Idempotent

Return one single-use Ausca CDP relay URL for a ready lease. The URL expires after 60 seconds, only one CDP connection may be live, and no more than eight tickets may be issued per lease. Supply the lease bearer on the HTTP or MCP transport; never place it in tool arguments. The upstream provider URL and credential are never disclosed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
idempotency_keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYes
connectionYes

Schema Changelog

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

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description reveals concrete behavioral traits: 60-second expiry, only one live CDP connection, up to eight tickets per lease, and no disclosure of upstream credentials. These details give the agent a much richer operational model than the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with the core purpose front-loaded, followed only by operationally relevant constraints and security guidance. Every sentence earns its place; there is no filler or redundancy.

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?

The description thoroughly covers purpose, readiness conditions, limits, auth handling, and secrecy. However, it leaves the required parameters completely undocumented in both the schema and description, so an agent must infer what session_id and idempotency_key represent in relation to the lease.

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%, yet the description never mentions session_id or idempotency_key, nor how they relate to the lease. The regex patterns in the schema provide some format guidance, but the description does not compensate for the missing semantics.

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?

The description states a precise verb and resource: 'Return one single-use Ausca CDP relay URL for a ready lease.' It also adds distinguishing constraints (expiry, one connection, ticket cap) that separate it from sibling tools like ausca_browser_session_close and ausca_browser_session_status.

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?

It clearly says when the tool applies ('for a ready lease') and gives an explicit usage rule: supply the lease bearer on the transport and never in tool arguments. It does not name alternative tools or exclusion conditions, but the context is sufficient for correct use.

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

All Ausca 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

A3.9/5.0
Disambiguation5/5

Each tool targets a clearly separate operation within its domain: inbox read/list/attachment/status/delete are all distinct, browser connect/status/close are unambiguous, and offer/invocation tools each have unique responsibilities. Descriptions reinforce the boundaries, so an agent should not struggle to select the right tool.

Naming Consistency2/5

Naming is divided into two patterns: resource-first names like ausca_agent_inbox_read and ausca_browser_session_close, versus verb-first names like ausca_get_invocation and ausca_search_offers. Within the inbox and browser groups, endings mix nouns (messages, status, attachment) and verbs (delete, read, connect), making the convention inconsistent across the set.

Tool Count5/5

13 tools is well within the ideal range for a multi-domain server, and each tool covers a meaningful operation without redundancy. The count supports inbox, browser session, and offer/invocation workflows without feeling bloated or sparse.

Completeness4/5

The inbox and browser-session clusters cover their core lifecycles well, and the offer/invocation cluster supports search, detail, preparation, state read, and cancellation. The main gap is the lack of an explicit submit/execute invocation tool, though invocation submission may be intentionally externalized; this is a minor workaround rather than a fatal dead end.

Resources