Skip to main content
Glama
Sign In

NetActuate

by com.netactuate
OverviewDiscussionsAdmin

List NetActuate's marketplace partners

list_marketplace_partners
Read-only

Lists the software vendors with listings in NetActuate's marketplace, such as Wowza, Broadpeak, NETINT, Ant Media and Red5 Pro: each with its slug, name, one-line description, website, the opening paragraph of its marketplace page, its listings (slug and name) and the netactuate.com URL of its page. 'Open Source' is the marketplace's grouping of open-source projects, marked isVendor: false. Takes no arguments. Use for 'who are NetActuate's media technology partners' or 'which vendors' software can I run on NetActuate'. For one vendor's listings in detail, find_marketplace_apps with vendor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare this is a safe read-only, closed-world listing, so the description does not need to restate safety. It adds meaningful behavioral context by explaining the returned fields and the special 'Open Source' grouping with isVendor: false, though it does not discuss ordering or result-size behavior.

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 with purpose and then moves through return shape, special-case grouping, and usage alternatives. It is somewhat long because of the vendor examples and field enumeration, but every part is relevant and no sentence is clearly wasteful.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so well: it names the vendor fields, listing fields, and page URL. Combined with zero parameters and read-only annotations, the definition is complete enough for an agent to call it correctly.

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 takes zero parameters, so the schema baseline is 4. The description reinforces this with 'Takes no arguments,' but there are no parameters for it to add semantic detail beyond that.

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 a specific verb and resource ('Lists the software vendors with listings in NetActuate's marketplace') and enumerates real examples and returned fields. It clearly distinguishes itself from find_marketplace_apps by framing this tool as the vendor-level list rather than a detail lookup.

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 gives explicit trigger phrases ('who are NetActuate's media technology partners') and directly routes the agent to find_marketplace_apps when the user needs one vendor's listings in detail. The when-to-use vs. alternative split is unambiguous.

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

All NetActuate 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