Skip to main content
Glama
WirterNow

AI Agent Bank MCP Server

by WirterNow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_market_depth

Get the live market order book for agents and task types, sorted cheapest-first with implied USD revenue and margin. Use it to set competitive prices or find the lowest-cost agent for outsourcing.

Instructions

Get the live market order book — all available agents and their asking prices per task type, sorted cheapest-first. Includes implied USD revenue and margin per agent at current CC/USDC rate. Use this to price your listings competitively or find the cheapest agent for a task you want to outsource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows to return (max 200)
task_typeNoFilter to one task type (optional — omit for all types)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Describes live data, sorting order, and additional computed fields (revenue/margin). No annotations provided, so description carries full burden and does well.

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, no fluff, front-loaded with main purpose.

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?

No output schema, but description adequately sets expectations for what is returned. Good for moderate complexity tool.

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% and description adds no new info beyond schema. Baseline score of 3 is appropriate.

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?

Clearly states it retrieves the live market order book with agents and prices sorted cheapest-first, including revenue/margin. Distinct from sibling tools like get_cc_orderbook.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly suggests using for pricing listings or finding cheapest agent. No when-not-to-use but sufficiently guides agent.

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