Skip to main content
Glama

List my utilities

list_utilities
Read-only

List the utilities your owner already has, shared by all your owner's agents. Newest first, no paging. Each entry gives the instance_id its tools take, kind, status (active, expired or suspended), expires_at, its URLs (an inbox's public URL) and how_to (which tools to call); unsubscribe lists also give their site_name. Filter with kind; get_utility shows one with its usage. A new one: search_catalog finds it and buy gets it, after your human says yes.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "locker"
    },
    "name": "list_utilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly utilities of this kind.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "kind": "locker"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "inbox",
      -  "locker",
      -  "wakeup",
      -  "share",
      -  "forms",
      -  "ask",
      -  "uptime",
      -  "blueprint",
      -  "heartbeat",
      -  "reminder",
      -  "inbox_pro",
      -  "queue",
      -  "suppression"
      -]New value: +[
      +  "inbox",
      +  "locker",
      +  "wakeup",
      +  "share",
      +  "forms",
      +  "ask",
      +  "uptime",
      +  "blueprint",
      +  "heartbeat",
      +  "reminder",
      +  "inbox_pro",
      +  "queue",
      +  "suppression",
      +  "site_badge"
      +]
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "inbox",
      -  "locker",
      -  "wakeup",
      -  "share",
      -  "forms",
      -  "ask",
      -  "uptime",
      -  "blueprint",
      -  "heartbeat",
      -  "reminder",
      -  "inbox_pro",
      -  "queue"
      -]New value: +[
      +  "inbox",
      +  "locker",
      +  "wakeup",
      +  "share",
      +  "forms",
      +  "ask",
      +  "uptime",
      +  "blueprint",
      +  "heartbeat",
      +  "reminder",
      +  "inbox_pro",
      +  "queue",
      +  "suppression"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "inbox",
      -  "locker",
      -  "wakeup",
      -  "share",
      -  "forms",
      -  "ask",
      -  "uptime",
      -  "blueprint"
      -]New value: +[
      +  "inbox",
      +  "locker",
      +  "wakeup",
      +  "share",
      +  "forms",
      +  "ask",
      +  "uptime",
      +  "blueprint",
      +  "heartbeat",
      +  "reminder",
      +  "inbox_pro",
      +  "queue"
      +]
  6. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / kind / description
      Added value: +"Only utilities of this kind."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  7. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description goes well beyond that: ordering (newest first), absence of paging, the exact per-entry fields, the legal status values (active/expired/suspended), and the kind-specific extra field for unsubscribe lists. That is concrete behavioral context an agent cannot get from the 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?

Front-loaded with purpose, then return shape, then routing to alternatives; no wasted sentences. The clipped, telegraphic phrasing ('A new one: search_catalog finds it and buy gets it') packs information but costs some readability.

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?

No output schema exists, so the description carries the return-value burden and does so fully — enumerating instance_id, kind, status, expires_at, URLs, how_to and the unsubscribe site_name. Necessary context for correct invocation of this two-param, single-filter read tool is present.

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 both parameters and the full kind enum are already documented in the schema. The description only echoes the filtering behavior ('Filter with kind') and says nothing about passport_token, so it adds little beyond the structured data — baseline 3.

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 and resource ('List the utilities your owner already has') plus scope ('shared by all your owner's agents'), which separates it cleanly from get_utility (one utility with usage) and from search_catalog/buy (new ones). An agent can pick this tool without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: use this to enumerate, 'get_utility shows one with its usage' for details, and 'search_catalog finds it and buy gets it, after your human says yes' for acquisition, including the human-approval precondition. Both alternatives and the condition selecting each are named.

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.