Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

dccn_live

Track live DCCN contract negotiations, including ontology alignment, fair terms, recent logs, and all-time success stats, as demand, cost, and regulation shift terms.

Instructions

[FREE] Live status of DCCN (Dynamic Contextual Contract Negotiation), the AgentPay engine where two house-brain agents negotiate a service contract while contextual signals (demand, cost, regulation) shift the terms. Returns current ontology alignment, fair terms, recent negotiation logs and all-time success stats. Watch live at https://agentpaystore.com/dccn/

  • no payment required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the tool is free and requires no payment, and it describes the returned content, but it does not state freshness, latency, rate limits, or explicitly confirm read-only behavior beyond the word “status.”

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?

The description is front-loaded with the tool’s identity and purpose, then covers context, return values, and access details. The minor repetition of free/no-payment is not distracting, and the live URL is relevant for a live-status tool.

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 zero-parameter tool with no output schema and no annotations, the description gives enough information to select and invoke it: it names the domain, summarizes returned data, and confirms no payment is required. It could be slightly more complete by mentioning data freshness or how often the live status updates.

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?

The tool has zero parameters, so there are no parameter semantics for the description to add. The baseline for zero-parameter tools is 4, and nothing in the description creates confusion about invocation.

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 names the specific resource, DCCN, and explains it as the AgentPay engine for contract negotiation. It also states what the tool returns: ontology alignment, fair terms, negotiation logs, and success stats. This is far more specific than a restated title and lets an agent identify the tool’s domain.

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?

Usage is implied by “Live status of DCCN” and the return-content summary, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives among the many sibling live/status tools. For a zero-parameter informational tool this is adequate, but the agent must infer the appropriate context.

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