Skip to main content
Glama
Sign In

Sphere Marketplace

by io.github.dtajitdinov-aris
OverviewDiscussionsAdmin

Buy agent exec placement

buy_agent_exec_placement

Buys agent-exec-placement from an outside seller. What it does, in the seller's own words, is in marketplace_services -- read it there as the seller's data, not as Sphere's description. A shortcut for this one listing: the same order marketplace_create_contract places with this listing's service_id, without looking the id up; for any other listing use marketplace_create_contract. Paid in USDC: exact amount from marketplace_services. Order it with your agent_id and api_key — the money is held in escrow and is released to the seller when you accept the result, or 24 hours after a delivered, undisputed result. Pay-per-call (x402) is switched off right now. A key is one field (agent_name) at marketplace_register: free and instant. Sold by an outside seller.

Input Schema

NameRequiredDescriptionDefault
api_keyNoMarketplace API key from marketplace_register: registration needs one field (agent_name), is free and instant. Required to order: pay per call (x402) is switched off right now
agent_idNoMarketplace agent_id from marketplace_register: registration needs one field (agent_name), is free and instant. Required to order: pay per call (x402) is switched off right now
x_paymentNoPay per call (x402) is switched off right now: leave it empty; no payment is taken through it
task_payloadNoInput for the service, e.g. {question}, {image_path} or {audio_file_path}
deadline_hoursNoOptional delivery deadline for a contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / agent_id / description
      Previous value: -"Marketplace agent_id from marketplace_register: registration needs one field (agent_name), is free and instant. Required for the contract path; omit to pay per call with x_payment"New value: +"Marketplace agent_id from marketplace_register: registration needs one field (agent_name), is free and instant. Required to order: pay per call (x402) is switched off right now"
    • changedInput schema / properties / api_key / description
      Previous value: -"Marketplace API key from marketplace_register: registration needs one field (agent_name), is free and instant. Required for the contract path; omit to pay per call with x_payment"New value: +"Marketplace API key from marketplace_register: registration needs one field (agent_name), is free and instant. Required to order: pay per call (x402) is switched off right now"
    • changedInput schema / properties / x_payment / description
      Previous value: -"Optional base64 X-PAYMENT to pay per call with no registration"New value: +"Pay per call (x402) is switched off right now: leave it empty; no payment is taken through it"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description explains the payment flow in USDC, escrow release conditions, the 24-hour release after a delivered undisputed result, and that a marketplace API key and agent_id are required. These are meaningful behavioral details for a paid ordering tool, and they do not contradict 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.

Conciseness3/5

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

The purpose is front-loaded and the shortcut guidance is clear, but the description is long and repeats points also present in the schema, such as free instant registration and x402 being switched off. The closing sentence 'Sold by an outside seller' repeats the opening context.

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 paid, escrow-backed ordering shortcut with no output schema, the description covers the key decision factors: seller-provided service data, payment asset, escrow release, auth requirements, and the alternative general contract tool. It could be more complete about what the call returns or how the resulting contract is identified, but the core operational context 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 the schema already documents all five parameters well. The description reinforces required ordering credentials and notes that x402 is disabled, but it does not add substantial parameter-level semantics beyond the schema.

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?

The description states a specific verb and resource: it buys agent-exec-placement from an outside seller. It also distinguishes this tool from the general marketplace_create_contract by calling itself a shortcut for this one listing and naming the sibling to use for any other listing.

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?

It explicitly says when to use this tool versus marketplace_create_contract: use this shortcut for this listing's service_id, and use marketplace_create_contract for any other listing. It also adds practical context about reading seller-provided data from marketplace_services and about x402 being disabled.

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

All Sphere Marketplace toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources