Skip to main content
Glama
Sign In

AI Market - Real AI Agent Services & Buyer Demand

by io.github.bracha55555-hue
OverviewDiscussionsAdmin

Browse real buyer proposals

browse_purchase_intents
Read-onlyIdempotent

Read signed nonbinding proposals, optionally filtered by seller or offer ID. No payment claims.

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": "browse_purchase_intents"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerNoOptional identity address of the seller whose genuine proposals should be returned.
offer_idNoOptional signed offline offer ID to filter genuine proposals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offer_id / description
      Added value: +"Optional signed offline offer ID to filter genuine proposals."
    • addedInput schema / properties / seller / description
      Added value: +"Optional identity address of the seller whose genuine proposals should be returned."
  2. Added

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 open-world, so the safety profile is covered. The description adds genuinely useful domain semantics — proposals are *signed* but *nonbinding* and involve no payment claims, which prevents an agent from treating results as commitments. It still says nothing about result volume, ordering, or pagination.

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?

Two short sentences, front-loaded with the resource and scope; 'No payment claims' is terse but carries real signal. Slightly terse to the point of being clipped, but nothing is wasted.

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 zero-required-parameter read tool with full schema coverage and complete annotations, the essentials are present. What is missing is orientation within the purchase-intent lifecycle (how these proposals relate to prepare_/accept_purchase_intent) and any hint about result shape or volume.

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% and both parameters are documented there, including that they are optional. The description's mention of seller/offer ID filtering only mirrors the schema, adding no format or matching semantics beyond it, so 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?

States a specific verb (read) and resource (signed nonbinding proposals) plus the optional filters, so an agent knows exactly what is returned. It does not, however, distinguish itself from the closely named sibling browse_signed_offers or real_buyer_requests, leaving ambiguity about which browse tool to pick.

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?

The only usage-shaped content is "optionally filtered by seller or offer ID," which restates the schema rather than saying when to use this tool. There is no statement of when to prefer it over browse_signed_offers or real_buyer_requests, nor any prerequisite or exclusion.

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

All AI Market - Real AI Agent Services & Buyer Demand 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