Skip to main content
Glama

Able and Agent Sandbox

Read an errand (ACT)

get_act
Read-onlyIdempotent

One of your ACTs as it stands, as GET /api/v1/acts/{id}. A DRAFT waits for your Principal's approval at approval.url, its page in the app: give them that link exactly as written. When you tell your Principal about it, call it an errand (ACT) the first time, and write its id as the site shows it, without act_: aTdTkM-48271.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_act"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ACT's id, with or without act_, such as aTdTkM-48271; a test errand's whole, test- included.
keyNoYour key, aak_…, when you cannot send it in the Authorization header. The sandbox only; on the live site the header alone is read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The ACT's id, with or without act_, such as aTdTkM-48271."New value: +"The ACT's id, with or without act_, such as aTdTkM-48271; a test errand's whole, test- included."
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The ACT's id, such as act_aTdTkM-48271."New value: +"The ACT's id, with or without act_, such as aTdTkM-48271."
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond that: a DRAFT carries an approval.url whose link must be passed to the Principal exactly as written, and naming rules for the ACT. It still says nothing about what a non-DRAFT ACT contains or any failure behavior.

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?

It is short and front-loads the read semantics before the DRAFT and naming instructions. The conversational asides ('One of your ACTs as it stands', the id example restated) add a little noise but nothing is seriously padded.

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?

With no output schema, the description must convey return content, and it only covers the DRAFT case via approval.url. It leaves a non-DRAFT ACT's fields unexplained, and the sandbox-vs-live key behavior is left to the schema, so it is adequate but not complete.

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 coverage is 100%, and both the id format (with or without act_, including the test-errand variant) and the key fallback are documented in the schema itself. The description only reiterates the id format example rather than adding meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource via the URL mapping 'GET /api/v1/acts/{id}', making clear this fetches a single ACT rather than a list. The phrasing 'One of your ACTs as it stands' is idiosyncratic but still readable as a single-record read, and the singular/plural distinction from list_acts is implied by the path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this tool over list_acts or other siblings, and no prerequisites or exclusions. The only procedural guidance concerns what to do with a DRAFT's approval.url after the call, which is output handling, not tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources