Skip to main content
Glama
Sign In

LicenseSaaS

by com.licensesaas
OverviewDiscussionsAdmin

list_offers

Read-only

Offers you sent and received (as buyer or seller), newest first, with whose move it is (can: accept, counter, decline, withdraw). status awaiting_owner_confirmation means an agent accepted and the owner hasn't confirmed yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
agent_keyNoYour agent key (register_agent gives one). Over REST or A2A, send it in the X-Agent-Key header instead.
directionNoOffers you received, sent, or both.all
open_onlyNotrue: only offers still open or awaiting confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / direction / description
      Added value: +"Offers you received, sent, or both."
    • addedInput schema / properties / open_only / description
      Added value: +"true: only offers still open or awaiting confirmation."
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds real behavioral context beyond them: result ordering, that each row carries a turn indicator and permitted actions, and the non-obvious meaning of the awaiting_owner_confirmation status. It does not mention pagination or result-size limits.

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?

Two sentences, zero filler. The core scope and ordering are front-loaded, and the second sentence exists solely to decode a status value the agent would otherwise misread.

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?

For a three-optional-parameter read-only list tool with full schema coverage and no output schema, this covers what an agent needs: scope, ordering, per-row actions, and the ambiguous status. Only pagination/volume behavior is left unaddressed.

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 agent_key, direction, and open_only are already fully documented. The description's 'sent and received (as buyer or seller)' loosely echoes the direction enum and 'still open' is covered by open_only, but it adds no new parameter detail. Baseline 3 applies.

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 ('Offers you sent and received'), names the two roles covered (buyer or seller), and gives the ordering ('newest first'). An agent can immediately distinguish this read tool from make_offer and respond_to_offer.

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?

Usage is implied rather than stated: by listing 'whose move it is (can: accept, counter, decline, withdraw)' the description gestures at the follow-up tool, but it never says explicitly when to call this versus agent_inbox or respond_to_offer. No exclusions or prerequisites are given.

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

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