Skip to main content
Glama
Sign In

EVUUN

by com.evuun
OverviewDiscussionsAdmin

List Business Imports

evuun_list_business_imports
Read-onlyIdempotent

Recover committed catalogue batches after an interrupted response or restart. Requires products:read. Newest first, bounded owner-only cursor. These are import outcomes, not publication or current product versions.

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

Input Schema

NameRequiredDescriptionDefault
afterNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Adds meaningful context beyond the annotations: requires products:read, results are newest first, cursor is owner-only and bounded, and results are import outcomes rather than publication/current product versions. The safety annotations already cover read-only/idempotent behavior, so this is strong added value.

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?

Four short sentences, front-loaded with the purpose and immediately followed by permission, ordering/cursor behavior, and semantic scope. No wasted text.

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 read-only list tool with annotations and no output schema, the description covers purpose, permission, ordering, cursor bounds, and semantic scope. It could say more about the limit parameter or return shape, but it is largely complete for correct invocation.

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 0%, so the description must carry parameter meaning. It implies cursor semantics with 'bounded owner-only cursor' and ordering with 'Newest first', but does not explain the 'after' parameter, its format, or the 'limit' parameter. It adds some meaning, but leaves gaps.

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

Purpose4/5

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

States a specific resource and scope: committed catalogue batches / import outcomes. It distinguishes this from publication or current product versions, so an agent can tell it is not the same as listing products. The verb is less direct than 'list', but the purpose is still clear.

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?

Gives an explicit use case: recover after an interrupted response or restart. It also states the required permission and clarifies what these results are not. No explicit alternative sibling is named, but the usage context is clear.

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

All EVUUN toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources