ausca_get_invocationRead the authoritative durable state, output commitment, and receipt reference for one invocation without creating a new purchase or retry identity.
| Name | Required | Description | Default |
|---|---|---|---|
| invocation_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / $defs / ArtifactEvidence / properties / artifact_refRemoved value: -{
- "$ref": "#/$defs/ArtifactRef"
-}Output schema / $defs / ArtifactEvidence / properties / artifact_uriAdded value: +{
+ "$ref": "#/$defs/ArtifactUri"
+}Output schema / $defs / ArtifactEvidence / requiredPrevious value: -[
- "artifact_ref",
- "content_digest",
- "media_type",
- "size_bytes",
- "created_at"
-]New value: +[
+ "artifact_uri",
+ "content_digest",
+ "media_type",
+ "size_bytes",
+ "created_at"
+]Output schema / $defs / ArtifactRefRemoved value: -{
- "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
- "maxLength": 512,
- "minLength": 1,
- "type": "string"
-}Output schema / $defs / ArtifactUriAdded value: +{
+ "description": "Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract.",
+ "maxLength": 512,
+ "minLength": 1,
+ "type": "string"
+}Output schema / $defs / ArtifactRef / descriptionAdded value: +"Opaque artifact reference minted by artifact commitment. Relay it unchanged; its form is not part of the contract."Output schema / $defs / ArtifactRef / maxLengthAdded value: +512Output schema / $defs / ArtifactRef / minLengthAdded value: +1Output schema / $defs / ArtifactRef / patternRemoved value: -"^runx:artifact:sha256:[a-f0-9]{64}$"Output schema / $defs / ReceiptReference / properties / uri / descriptionAdded value: +"Opaque receipt identity minted by the notary. Relay it unchanged; its form is not part of the contract."Output schema / $defs / ReceiptReference / properties / uri / minLengthPrevious value: -14New value: +1Output schema / $defs / ReceiptReference / properties / uri / patternRemoved value: -"^runx:receipt:.+$"Output schema / $defs / ArtifactEvidenceAdded value: +{
+ "additionalProperties": false,
+ "properties": {
+ "artifact_ref": {
+ "$ref": "#/$defs/ArtifactRef"
+ },
+ "content_digest": {
+ "$ref": "#/$defs/Digest"
+ },
+ "created_at": {
+ "format": "date-time",
+ "type": "string"
+ },
+ "media_type": {
+ "maxLength": 200,
+ "minLength": 1,
+ "type": "string"
+ },
+ "size_bytes": {
+ "maximum": 26214400,
+ "minimum": 1,
+ "type": "integer"
+ }
+ },
+ "required": [
+ "artifact_ref",
+ "content_digest",
+ "media_type",
+ "size_bytes",
+ "created_at"
+ ],
+ "type": "object"
+}Output schema / $defs / ArtifactRefAdded value: +{
+ "pattern": "^runx:artifact:sha256:[a-f0-9]{64}$",
+ "type": "string"
+}Output schema / $defs / InvocationFailureAdded value: +{
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "maxLength": 96,
+ "minLength": 1,
+ "type": "string"
+ },
+ "message": {
+ "maxLength": 500,
+ "minLength": 1,
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+}Output schema / $defs / InvocationState / properties / failureAdded value: +{
+ "$ref": "#/$defs/InvocationFailure"
+}Output schema / $defs / InvocationState / properties / output_artifactAdded value: +{
+ "$ref": "#/$defs/ArtifactEvidence"
+}Output schema / $defs / ReceiptReference / properties / public_urlAdded value: +{
+ "description": "Unguessable public verification page for the privacy-bounded hash-only proof. It reveals the receipt digest, service, public price, and completion time, but not input bytes, output bytes, or their content digests.",
+ "format": "uri",
+ "maxLength": 2048,
+ "pattern": "^https://[^?#]+/r/[a-f0-9]{64}$",
+ "type": "string"
+}Output schema / $defs / ReceiptReference / properties / public_urlRemoved value: -{
- "description": "Unguessable public verification page for the privacy-bounded hash-only proof. It reveals the receipt digest, service, public price, and completion time, but not input bytes, output bytes, or their content digests.",
- "format": "uri",
- "maxLength": 2048,
- "pattern": "^https://[^?#]+/r/[a-f0-9]{64}$",
- "type": "string"
-}Output schema / $defs / ReceiptReference / properties / public_urlAdded value: +{
+ "description": "Unguessable public verification page for the privacy-bounded hash-only proof. It reveals the receipt digest, service, public price, and completion time, but not input bytes, output bytes, or their content digests.",
+ "format": "uri",
+ "maxLength": 2048,
+ "pattern": "^https://[^?#]+/r/[a-f0-9]{64}$",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful side-effect clarity by stating it reads authoritative durable state and does not create a new purchase or retry identity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words; the key scope and side-effect constraint are stated immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and annotations cover safety/idempotency, so the description mainly needs to cover behavior. It does that well, though the missing invocation_id guidance is a minor completeness gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter, invocation_id, has no schema description (0% coverage). The description refers to “one invocation” but does not explain the identifier's expected source, format, or value beyond what the parameter name implies, so it fails to compensate for the schema gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Read) and resource (invocation state), and specifies the durable state, output commitment, and receipt reference. The clause about not creating a new purchase or retry identity helps distinguish it from prepare_invocation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is the read-side counterpart to purchase/retry operations by saying it does not create a new purchase or retry identity, but it does not name an alternative tool or explicitly state when to use this versus prepare_invocation or cancel_invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.