Skip to main content
Glama
Sign In
Yolfi

Yolfi

Official
by yolfinance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Update Yolfi Organization

yolfi_organization_update

Update organization profile fields like display name, support email, logo URL, fee payer, and email notification settings through the existing Yolfi organization endpoint.

Instructions

Update organization profile fields through the existing Yolfi organization endpoint. Do not invent merchant identity, support email, or settlement settings.

Input Schema

NameRequiredDescriptionDefault
nameNoMerchant or project display name approved by the user.
emailNoMerchant support or account email approved by the user.
logoUrlNoExisting or owner-approved public organization logo URL.
feePayerNoOwner-approved party paying the platform fee.
disableAllEmailNotificationsNoOwner-approved setting to disable all organization email notifications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.1
    • addedInput schema / properties / disableAllEmailNotifications
      Added value: +{
+  "description": "Owner-approved setting to disable all organization email notifications.",
+  "type": "boolean"
+}
    • addedInput schema / properties / feePayer
      Added value: +{
+  "description": "Owner-approved party paying the platform fee.",
+  "enum": [
+    "MERCHANT",
+    "CUSTOMER"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / logoUrl
      Added value: +{
+  "description": "Existing or owner-approved public organization logo URL.",
+  "type": "string"
+}
    • removedInput schema / properties / webhookAdapter
      Removed value: -{
-  "description": "Webhook adapter output format. Use NONE unless the target app expects a compatible provider payload.",
-  "enum": [
-    "NONE",
-    "STRIPE",
-    "LEMON_SQUEEZY",
-    "PADDLE",
-    "POLAR",
-    "GUMROAD",
-    "DODO"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / webhookUrl
      Removed value: -{
-  "description": "HTTPS webhook endpoint in the target application. Ask the user if the backend URL is unknown.",
-  "type": "string"
-}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description adds real value with the 'do not invent merchant identity, support email, or settlement settings' guardrail, but says nothing about partial-update semantics (all five fields are optional) or what happens to unmentioned fields — important for a non-idempotent mutation.

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?

Two short sentences with the action front-loaded and the constraint second; no filler. It is arguably slightly too terse for a mutation tool, but nothing is wasted.

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?

For a five-parameter, zero-required mutation tool with no output schema, the description should clarify that omitted fields are left unchanged and whether the call returns the updated profile. Neither is addressed, leaving a meaningful gap despite the annotations covering the safety profile.

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 every parameter including the feePayer enum is documented in the schema. The description adds no format, defaulting, or partial-update detail beyond it, so baseline 3 applies.

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 and resource ('Update organization profile fields') and anchors it to 'the existing Yolfi organization endpoint', which distinguishes it from sibling reads like yolfi_organization_get. It also gestures at the boundary with yolfi_settlement_configure by forbidding settlement changes, though that exclusion is framed as a caution rather than a scope statement.

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?

Usage is implied rather than stated: 'through the existing Yolfi organization endpoint' and 'Do not invent...' tell the agent how to behave, but there is no explicit when-to-use vs. yolfi_organization_get or yolfi_settlement_configure, and no prerequisites. The 'do not invent' clause functions as a constraint, not routing guidance.

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