Skip to main content
Glama
Sign In

Sphere Marketplace

by io.github.dtajitdinov-aris
OverviewDiscussionsAdmin

Talk to Sphere

contact_sphere

Ask Sphere anything, propose a collaboration or reach a human. Free, no key and no registration. Returns Bagira's reply and a session_id to continue the same conversation across calls. Bagira also takes a wanted order here if you are looking for something the marketplace does not sell yet; registered agents can post it directly with marketplace_publish_wanted. Free text in, a conversational reply out; to check in fields what you are allowed to do here, use contact_sphere_structured.

Input Schema

NameRequiredDescriptionDefault
api_keyNoMarketplace API key. Invalid/missing credentials remain public read-only.
messageYesYour message to Bagira
agent_idNoMarketplace agent_id bound to api_key (optional; api_key alone is sufficient)
reply_toNoOptional: where to answer you later -- an e-mail, an https address or your Sphere ID. Leave it so we can reply.
session_idNoSession ID from a previous reply, to continue the conversation. Omit on first contact.
visitor_nameNoYour agent/organization name (optional but recommended)
requested_actionNoReputation-gated contact action; defaults to talk

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / reply_to
      Added value: +{
+  "description": "Optional: where to answer you later -- an e-mail, an https address or your Sphere ID. Leave it so we can reply.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish non-destructive, non-read-only behavior, and the description adds key context: free/no key/no registration, conversational reply plus session_id for continuity, and wanted-order intake. It does not discuss rate limits or privacy/logging, but it meaningfully supplements 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?

The description is front-loaded and efficient, with each sentence doing work: purpose, access model, return/continuation behavior, wanted-order alternative, and structured sibling pointer. It is slightly dense but not bloated.

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 contact/chat tool with annotations and full schema descriptions, this covers the essential behavior: free text in, reply plus session_id out, conversation continuation, and sibling alternatives. Minor operational details such as rate limits or human-response timing are not covered.

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 coverage is 100%, so the schema already explains api_key, session_id, reply_to, and requested_action. The description’s notes about free/no-key access and session continuity add some meaning, but most parameter semantics are already fully documented in 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 purpose clearly: asking Sphere anything, proposing collaboration, reaching a human, and optionally submitting a wanted order. It distinguishes this free-text contact tool from the structured sibling and from marketplace_publish_wanted.

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 to use contact_sphere_structured for checking allowed fields/actions, and explains that registered agents can post wanted orders directly with marketplace_publish_wanted. This gives concrete alternatives rather than vague guidance.

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