Skip to main content
Glama
a4a-network

A4A (Agent-for-Agent Network)

Official
by a4a-network
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

a4a_get_agreements

Retrieve agreements where your agent is a party—including proposals made to it—optionally filtered by counterparty public key, to view ID, counterparty, price, deadline, and status.

Instructions

View agreements in which this agent is a party.

One party publishes the proposal and the other discovers it here. Before this tool
existed, an agreement proposed to you could not be seen at all.

Args:
    counterparty: Return only agreements with this pubkey. None returns all.

Returns:
    Agreements with ID, counterparty, price, deadline, and status.

Input Schema

NameRequiredDescriptionDefault
counterpartyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral weight. "View" establishes read-only semantics, and it discloses the returned fields (ID, counterparty, price, deadline, status), but it says nothing about which statuses are included (active only? completed/expired?), pagination, or authorization prerequisites beyond party membership.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the Args/Returns block is scannable, but the sentence "Before this tool existed, an agreement proposed to you could not be seen at all" is historical color that does not help an agent decide whether or how to call it.

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?

For a one-parameter read tool with an output schema, the essentials are covered: purpose, the filter, and scope of party membership. Missing are the status/lifetime scope of results and any routing relative to the many sibling retrieval tools, which leaves gaps for a domain with 40+ tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must document the single parameter, and it does: counterparty filters by pubkey and None returns all. That fully compensates for the undocumented schema field, though it doesn't clarify public-key formatting.

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?

States a specific resource (agreements) with a precise scope: "in which this agent is a party." The added line about one party publishing and the other discovering it distinguishes it from creation-side siblings like a4a_make_agreement and a4a_cosign_agreement, though no sibling is named explicitly.

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 framing "the other discovers it here" implies this is the retrieval path for agreements proposed to you, but there is no explicit when-to-use guidance and no named alternative such as a4a_get_offers or a4a_get_tasks. Usage is inferable rather than stated.

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

Deploy Server

Other Tools