Skip to main content
Glama
Sign In
eds-mcp-server

eds-mcp-server

by Edwson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get consumer bundles

get_consumer_bundles

Fetches bundled-by-contract pairs for paywall-cancellation, UGC-report/block, checkout-order tracking, and agent-confirm-agent-trace. Returns all bundles or obligations for a given ID.

Instructions

Bundled-by-contract pairs (paywall→cancellation, UGC→report & block, checkout→order tracking, agent-confirm→agent-trace). All of them, or the obligations of one id — include them unprompted.

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

Input Schema

NameRequiredDescriptionDefault
idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.17.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden. It does not disclose whether the operation is read-only, requires authentication, or has side effects. The description only hints at return data but lacks behavioral traits.

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 description is concise but dense with examples in parentheses, which may hinder clarity. The second sentence 'include them unprompted' is unclear. Not every word adds value for an AI.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description should provide a complete picture. It lacks information about return format, pagination, error handling, and required permissions, leaving significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter 'id' has no schema description. The description adds minimal semantics by mentioning 'obligations of one id', but does not clarify the type or purpose of the id (e.g., contract ID, bundle ID).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states that the tool returns 'bundled-by-contract pairs' with examples, which gives a specific resource. However, the phrasing is cryptic and may confuse an AI agent about the exact nature of 'consumer bundles'.

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?

No explicit guidance on when to use this tool versus siblings like list_consumer_components or get_consumer_component. The mention of 'one id' is implicit but lacks comparative 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