Skip to main content
Glama

Numonic

by ai.numonic
OverviewDiscussionsAdmin

GetCollectionPublicUrls

Get publication status and public URLs for all assets in a collection. Returns whether the collection is published, publication metadata, and URLs for each published asset.

Input Schema

NameRequiredDescriptionDefault
tenant_idNoOptional: UUID of the tenant. Omit it: the server uses the tenant your credential (OAuth connection or API key) is bound to. A tenant_id that differs from the credential's tenant is rejected.
collection_hYesCollection hash (SHA-1, 40 hex chars) to get public URLs for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / tenant_id / description
      Previous value: -"UUID of the tenant"New value: +"Optional: UUID of the tenant. Omit it: the server uses the tenant your credential (OAuth connection or API key) is bound to. A tenant_id that differs from the credential's tenant is rejected."
    • changedInput schema / required
      Previous value: -[
-  "tenant_id",
-  "collection_h"
-]New value: +[
+  "collection_h"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does disclose the return payload (published flag, publication metadata, per-asset URLs), which is real behavioral content, but it says nothing about permissions, cost, or whether any state changes.

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 front-loaded sentences with zero filler: the first states the action and scope, the second enumerates the return contents. Both sentences earn their place, especially given there is no output schema.

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 simple two-parameter read tool with a fully documented schema, the description covers purpose and return shape (compensating for the absent output schema). It is slightly thin on authorization/prerequisite context, keeping it out of the top band.

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 100% for both parameters, so the schema already documents collection_h (SHA-1 format) and the tenant_id credential-binding rule. The description adds no format or constraint detail beyond that, which is the baseline 3 for fully-covered schemas.

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 verb+resource ('Get publication status and public URLs for all assets in a collection') and its scope ('all assets in a collection') distinguishes it from the singular sibling GetAssetPublicUrl. No sibling is named explicitly, so it stops short of a 5.

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?

The scope phrase implies when to use it (collection-wide publication lookup) versus the single-asset sibling, but there is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage is only implied.

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

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