Skip to main content
Glama

Ausca

by com.ausca
OverviewDiscussionsAdmin

Resolve an active or pinned offer revision

ausca_get_offer
Read-onlyIdempotent

Resolve one active offer or an exact immutable revision, including the schema and revision digests required to construct a valid invocation envelope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offer_idYes
revision_digestNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
offerYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / $defs / OfferSummary / properties / title / maxLength
      Previous value: -120New value: +80
  2. Changed5 schema fields changed
    • addedOutput schema / $defs / OfferSummary / properties / catalog_url
      Added value: +{
+  "const": "/catalog.json",
+  "type": "string"
+}
    • addedOutput schema / $defs / OfferSummary / properties / input_schema_url
      Added value: +{
+  "format": "uri-reference",
+  "type": "string"
+}
    • addedOutput schema / $defs / OfferSummary / properties / output_schema_url
      Added value: +{
+  "format": "uri-reference",
+  "type": "string"
+}
    • addedOutput schema / $defs / OfferSummary / properties / route
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "method": {
+      "const": "POST"
+    },
+    "path": {
+      "maxLength": 512,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "method",
+    "path"
+  ],
+  "type": "object"
+}
    • changedOutput schema / $defs / OfferSummary / required
      Previous value: -[
-  "offer_id",
-  "offer_revision",
-  "offer_revision_digest",
-  "input_schema_digest",
-  "output_schema_digest",
-  "title"
-]New value: +[
+  "offer_id",
+  "offer_revision",
+  "offer_revision_digest",
+  "input_schema_digest",
+  "output_schema_digest",
+  "title",
+  "route",
+  "input_schema_url",
+  "output_schema_url",
+  "catalog_url"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds value by explaining the active-versus-exact-revision behavior and clarifying that the result includes schema and revision digests needed for an invocation envelope.

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?

A single, focused sentence provides the operation, scope, and a useful output-oriented detail. There is no filler or redundant restatement of the title, and the most important semantic distinction is front-loaded.

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?

With a rich output schema and safety annotations already present, the description covers the key selection semantics and the reason for calling this tool. The only notable gap is the lack of explicit routing guidance toward sibling search tools, which is minor for a targeted lookup operation.

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 0%, so the description must compensate. It conveys the core difference between resolving an active offer versus an exact immutable revision, but it never explicitly names offer_id or revision_digest or explains which parameter selects which mode. The description adds partial meaning but does not fully carry the parameter documentation burden.

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 clearly identifies a specific operation: resolving one active offer or an exact immutable revision. It distinguishes itself from a search/list tool by pointing to single-offer semantics and ties the purpose to constructing an invocation envelope.

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 context of use is implied: use this when you need a specific active offer or exact revision, especially for building an invocation envelope. However, the description never explicitly states when to prefer a sibling like ausca_search_offers or ausca_prepare_invocation, and no exclusions are given.

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