Skip to main content
Glama

Singularity Layer MCP

by io.github.ivaavimusic
OverviewDiscussionsAdmin

update_endpoint

Update allowlisted endpoint fields such as metadata, pricing, listing flags, imagery, wallet, payment options, slug, and webhook settings. PATs are preferred and require mcp:endpoints:write or mcp:*.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoPricing mode
nameNoUpdated endpoint name
slugYesThe existing slug of the endpoint you want to update
chainNoUpdated chain/network
priceNoUpdated endpoint price
activeNoEnable or disable the endpoint
apiKeyNoLegacy endpoint API key (x402_*)
logoUrlNoUpdated logo URL
newSlugNoNew slug to assign to the endpoint
categoryNoUpdated category
currencyNoUpdated currency code
imageUrlNoUpdated image URL
isListedNoWhether the endpoint should be listed
bannerUrlNoUpdated banner URL
originUrlNoUpdated origin URL
webhookUrlNoSet an HTTPS webhook URL or null to remove it
accessTokenNoYour dashboard MCP personal access token (sgl_pat_*)
descriptionNoUpdated description
walletAddressNoUpdated payout wallet address
paymentOptionsNoUpdated payment options object
creditPackageSizeNoCredits per package
creditPackagePriceNoPackage price in USDC
listedInMarketplaceNoWhether the endpoint should appear in marketplace listings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / accessToken
      Added value: +{
+  "description": "Your dashboard MCP personal access token (sgl_pat_*)",
+  "type": "string"
+}
    • changedInput schema / properties / apiKey / description
      Previous value: -"Your endpoint API key (x402_*)"New value: +"Legacy endpoint API key (x402_*)"
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "direct",
-  "credits"
-]New value: +[
+  "direct",
+  "credits",
+  "flexible"
+]
    • changedInput schema / required
      Previous value: -[
-  "slug",
-  "apiKey"
-]New value: +[
+  "slug"
+]
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions PATs and required scopes, which is useful, but does not explain whether the update is partial or full replacement, side effects, reversibility, or response behavior. The term 'allowlisted' is not elaborated.

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 two sentences, front-loaded with the main action and resource. Every word adds value—listing field categories and auth requirements—with no filler or redundancy.

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

Completeness3/5

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

While the schema richly documents all 23 parameters, the description lacks key contextual information for a complex update tool: it does not clarify that only provided fields are updated, what 'allowlisted' means, or what the success/error response looks like. With no output schema, more behavioral context would be expected.

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%, so the schema documents all parameters. The description adds a high-level grouping of field categories but does not provide syntax or format details beyond the schema. It meets the baseline without significantly enhancing parameter understanding.

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 clearly states the verb 'Update' and the resource 'endpoint,' listing specific categories of fields (metadata, pricing, listing flags, etc.). This distinguishes it from sibling tools like update_campaign or update_product, and from specialized webhook tools.

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 description implies when to use the tool (to update endpoint fields) but does not explicitly mention alternatives or when not to use it. It provides auth context (PATs preferred with required scopes) but lacks direct comparison with set_webhook or remove_webhook for webhook-specific updates.

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

All Singularity Layer MCP 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