Skip to main content
Glama

DC Member API

by io.github.dynamitecircle

profile_update

PATCH /profile — Update profile fields

Update allowed profile fields. Only the fields you include will be changed. Location, photo, and gender cannot be updated via API.

⚠️ WRITE operation: this mutates your DC account data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dietNoDietary restrictions — used when DC plans event meals.
githubNoGitHub username only (no URL prefix). 1-39 chars per GitHub's rules: letters, digits, `-`. Required to be granted access to the public DC client repo — set this to opt in.
hobbiesNoYour non-business hobbies — games, camping, art, sports, anything (up to 1600 chars).
twitterNoTwitter/X username only (no URL prefix). 1-15 chars: letters, digits, `_`.
facebookNoFacebook username only (no URL prefix). 5-50 chars: letters, digits, `.`.
headlineNoOne-sentence elevator pitch shown at the top of your DC profile (max 64 chars).
linkedinNoLinkedIn username only (no URL prefix). 1-50 chars: letters, digits, `.`, `_`, `-`.
nicknameNoDisplay name override — what other DCers see in addition to your real name (max 256 chars).
teamSizeNoNumber of full-time and part-time team members in your primary business. Predefined bracket.
whatsAppNoWhatsApp phone number in international format — `+` followed by 5-16 digits, no dashes or spaces. Required if you want to be added to the DC WhatsApp community. Always private — only visible to DC staff.
expertiseNoAreas you might consider yourself an expert in — skills you can use to help other members (up to 1600 chars).
focusmateNoFocusmate username only (no URL prefix). 3-50 chars: letters, digits, `_`, `-`.
instagramNoInstagram username only (no URL prefix). 1-30 chars: letters, digits, `.`, `_`.
shirtSizeNoT-shirt size — used when DC sends event swag.
spouseNameNoName of your spouse or partner — used only for the DCBKK partner pass. Always private (DC staff only).
businessNameNoName of the main business you run or are primarily focused on right now (max 256 chars). You can list other businesses in `otherBusinesses`.
annualRevenueNoApproximate annual revenue (in U.S. dollars) of your primary business over the last 12 months. Predefined bracket.
businessWebsiteNoPublic website for your primary business — single URL only (max 256 chars).
otherBusinessesNoOther businesses you currently operate. Feel free to share URL, short description, and year started for each (up to 1600 chars).
yearsInBusinessNoHow long you have been on the entrepreneurial path. Used for matching with other members. Predefined bracket.
businessIndustryNoCategory your primary business fits into. Must be one of the predefined industries.
currentChallengeNoYour current business challenge or goal. Used internally to match you with other members who can help (up to 1600 chars).
peopleOfInterestNoWhat kinds of community members you would like to connect with. Used to send recommendations of relevant DCers (up to 1600 chars). Set `peopleOfInterestIsPrivate: true` to keep this visible only to DC staff.
relevantLocationsNoCities or regions you frequently visit. Helps surface trip overlaps with other members (up to 1600 chars).
teamSizeIsPrivateNoVisibility of your team size. `true` = hidden from other DCers (only DC staff can see it); `false` = visible to all DCers.
previousBusinessesNoPrevious business exits and entrepreneurial experience worth listing (up to 1600 chars).
askMeAnythingTopicsNoTopics other members can ask you about, in your field of expertise (up to 1600 chars).
businessDescriptionNoDescription of your primary business. Plain text or HTML, up to 1600 chars.
annualRevenueIsPrivateNoVisibility of your revenue. `true` = hidden from other DCers (only DC staff can see it); `false` = visible to all DCers.
peopleOfInterestIsPrivateNoVisibility of your "who I want to meet" answer. `true` = hidden from other DCers (only DC staff can see it); `false` = visible to all DCers.

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It correctly identifies the operation as a WRITE mutation to DC account data and states which fields are immutable. No contradictions.

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?

Description is front-loaded with the HTTP method and core purpose. It is compact (5 sentences) and covers key points without excess. Could potentially be more structured, but it's efficient.

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?

Given 30 parameters, no output schema, and no annotations, the description provides sufficient context: what the tool does, which fields are mutable, and the destructive nature. Adequate for an agent to use 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?

Schema has 100% coverage with individual parameter descriptions. The tool description adds context about PATCH semantics and immutable fields, which complements the schema well.

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 it updates profile fields via PATCH, with a specific verb and resource. It distinguishes itself from sibling tools like 'profile' (GET) and 'profile_match_create' (different action).

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?

Explicitly mentions that only included fields change and lists fields that cannot be updated via API (location, photo, gender). Provides a warning about mutation. However, it does not explicitly contrast with alternative tools like 'profile' for when to use this vs reading.

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

All DC Member API toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Despite the large number of tools, each has a detailed description that clearly distinguishes its purpose. Minor potential overlaps (e.g., search vs. resource-specific search, own vs. other's agenda) are well documented, so an agent can differentiate them.

Naming Consistency4/5

Tool names follow a consistent verb_noun or resource_subresource_action pattern in snake_case. A few tools are just nouns (e.g., 'alerts', 'announcements'), but these are top-level listing endpoints; overall the naming is predictable.

Tool Count2/5

85 tools is very high for a single server, making it difficult for an agent to efficiently explore and select the right tool. While each tool seems justified for the broad domain, the count feels overwhelming and could be streamlined.

Completeness3/5

The tool surface covers most major areas (events, trips, chapters, rooms, search, profile, etc.) with CRUD or lifecycle operations. However, the lack of a 'send message' tool for rooms is a notable gap, and some resources (e.g., events) are read-only on creation/update, limiting agent workflows.

Resources