Skip to main content
Glama

welance/directory

Server Details

Match a project brief with small vetted software teams, anonymously; sign in to manage your own.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
welance/directory

TDQS

A3.8/5.0

Scored across 20 tools

Disambiguation4/5

The tools mostly target clearly distinct resources and actions: briefs, pitches, bookings, profiles, teams, and invoices are separated, and propose/read/list/match/preview actions are generally distinguishable. The main possible confusion is between exploratory tools like match_brief, preview_teams, list_open_briefs, and read_pitchable_briefs, but their descriptions clarify the differences well.

Naming Consistency4/5

The set uses consistent snake_case throughout and mostly follows a verb_noun pattern (read_brief, propose_booking, list_open_briefs). Minor deviations include noun-phrase tools such as brief_rules and directory_capabilities, plus the slightly awkward ordering of propose_booking_accept.

Tool Count4/5

Twenty tools is slightly above the ideal range, but the domain is broad: public briefs, matching, pitches, bookings, profiles, teams, invoices, and rules. Most tools map to distinct operations, so the count is heavy but reasonable rather than bloated.

Completeness4/5

The surface covers the main marketplace lifecycle: browsing and matching briefs, drafting/publishing briefs, drafting/sending pitches, proposing/accepting bookings, managing profiles and teams, and reading invoices. However, lifecycle gaps remain for withdrawing pitches, cancelling bookings, closing briefs, and possibly creating teams.

Available Tools

20 tools
brief_rulesThe public scoring rulesA
Read-onlyIdempotent
Inspect

The rule catalogue a brief is scored against before teams see it: ids, labels, weights and the acceptance threshold that decides whether a brief publishes.

Inputs: no named parameters.

directory_capabilitiesWhat welance/directory isA
Read-onlyIdempotent
Inspect

What the directory is, who it is for (small vetted software teams for digital projects, especially ones rooted in the physical world), how pricing works (0% of the project; €30 + VAT from each side only to meet, charged once both accept a time), and the rule that the human stays the principal.

Inputs: no named parameters.

list_open_briefsOpen briefs and delivered projectsA
Read-onlyIdempotent
Inspect

The public briefs: open ones looking for a team, ones in vetting, and the archive of delivered projects with budget, sector and delivery team. Anonymised server-side. Filter by status or to tangible-world projects only.

Inputs: status, tangible.

match_briefShortlist teams for a draft briefA
Read-onlyIdempotent
Inspect

Match a draft brief (80–20000 characters) against the real, eligible anonymous teams: only teams the brief matches come back, with reasons and the defaults inferred from the brief. Same derivation and matcher as publishing, stores nothing, calls no LLM. Ends with a "Start this brief" link that opens the guided flow prefilled.

Inputs: brief (required), title, language.

preview_teamsA protected preview of the team boardA
Read-onlyIdempotent
Inspect

Two anonymous, vetted teams as specimens (rotating daily) and the size of the supply — never the whole board. The board is brief-first: the teams that fit a project are listed only against a draft brief. Names and members are revealed only after a mutual €30-per-side handshake.

Inputs: no named parameters.

propose_bookingPropose meeting timesAInspect

As the client of a pitch on the person's own brief (appId): a proposed 30-minute call with at least 3 concrete slots (ISO 8601; weekdays, on the hour, 09–18 CET, 3–10 business days ahead) and an optional note. Confirming holds €30 from the client's side for up to 7 days; nothing is charged until both sides accept a time. A no-show's €30 is not returned; the side that showed gets a credit. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: appId (required), slots (required), summary (required), note.

propose_booking_acceptPropose accepting a meeting timeAInspect

As the team on a booking (bookingId): a proposal to accept one of the client's offered slots (slotId). Accepting charges €30 from each side; if the client does not show, the team's €30 becomes a credit; if the team does not show, its €30 is not returned. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: slotId (required), summary (required), bookingId (required).

propose_brief_draftPropose a brief draftAInspect

A proposed update to the person's local brief draft: title, markdown, and/or per-rule answers. Accepting it fills the brief editor; nothing is published. The whole proposal is limited to 64,000 UTF-8 bytes. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: summary (required), title, answers, markdown.

propose_brief_publishPropose publishing a briefAInspect

A proposal to publish a brief (title, markdown, optional language) to the board. On confirmation the server's live score gate decides whether it publishes; publishing emails a one-time link and signs no one in. The whole proposal is limited to 64,000 UTF-8 bytes. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: title (required), summary (required), markdown (required), language.

propose_pitch_draftPropose a pitch draftAInspect

An anonymous pitch draft for one of the person's teams (teamKey) on an open brief (briefId). Accepting it fills the existing pitch editor; nothing is sent. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: text (required), briefId (required), summary (required), teamKey (required).

propose_pitch_sendPropose sending a pitchAInspect

A proposal to send an anonymous pitch for one of the person's teams (teamKey) on an open brief (briefId); once confirmed, the brief owner sees it. Each brief accepts a limited number of pitches (10). Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: text (required), briefId (required), summary (required), teamKey (required).

propose_profile_updatePropose profile changesAInspect

Proposed field changes to one entity. entity "person": the signed-in person's own profile (job_role, years_experience, langs, skills, hourly_rate). entity "member" + teamKey + memberKey: a confirmed colleague on one of the person's teams (job_role, years_experience, langs, hourly_rate; skills are rated only by their owner). entity "team" + teamKey: intro, based, remote, availability, langs, shipped, hourly. entity "organisation" + organisationId: website, description of an organisation the person owns or administers (descriptive only; it verifies nothing). Skills: changes[{field:"skills", value:[{name, rating 1–10}]}] adds or re-rates (an existing name takes the new rating); removeSkills lists skill names to remove. Languages: addLangs / removeLangs take two-letter codes; alternatively a langs change carries the complete new list (not both). Scalars: changes[{field, value}]; hourly_rate is EUR/h, 10–2000; team hourly overrides the rate blended from members' rates, and null restores the blend; team size is not a field (it is the confirmed member count). Team shipped: value lists entries to add, each {title, url, desc}; existing entries are kept; removeShipped lists titles or links to remove. inferred=true marks a value derived from evidence rather than stated by the person; hourly rate, availability, languages and skill ratings are rejected when inferred. Each changed field becomes a separate card the person approves. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: entity (required), summary (required), changes, teamKey, +6 more.

propose_team_invitePropose inviting someone to a teamAInspect

A proposal to invite a person to one of the signed-in person's teams (teamKey) by name and email, with an optional role. Once confirmed, the invitee receives an email; their skill ratings are theirs to set later. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.

Inputs: name (required), email (required), summary (required), teamKey (required), +1 more.

read_bookingOne bookingA
Read-onlyIdempotent
Inspect

One booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on.

Inputs: bookingId (required).

read_briefOne briefA
Read-onlyIdempotent
Inspect

One public brief in full, markdown body included, by its id (briefId).

Inputs: briefId (required).

read_invoicesMy invoicesA
Read-onlyIdempotent
Inspect

The signed-in person's past invoices with their PDF and document links (pdfUrl / documentUrl). Without filters it covers every billing identity of the person (personal VAT plus companies they own or administer); each invoice is tagged with its identity {kind, id, label, vatMasked}. identity ("all", "personal" or "org:") or identities (several of "personal" / "org:") narrow by identity; from/to (YYYY-MM-DD, inclusive) narrow by date; limit caps the count (1–50).

Inputs: to, from, limit, identity, +1 more.

read_my_pitchesMy briefs, pitches and bookingsA
Read-onlyIdempotent
Inspect

The signed-in person's pitches and bookings on both sides: applications sent by their teams (with handshake and booking state) and the anonymous pitches received on their own briefs.

Inputs: no named parameters.

read_my_teamsMy teamsA
Read-onlyIdempotent
Inspect

The signed-in person's teams: key (teamKey), name, and the facts the system derives rather than stores (members = confirmed people; rate = blended from members' rates unless the team sets an override; languages from members unless set); each team's profile (based, remote, availability, shipped work), open and matching brief counts, and a checklist of what pitching and the public board require, each marked met or missing.

Inputs: no named parameters.

read_pitchable_briefsBriefs my teams can pitch onA
Read-onlyIdempotent
Inspect

For each of the signed-in person's teams, the open briefs that team can still pitch on: not yet pitched, pitch slots left, and a language match.

Inputs: no named parameters.

read_profileMy profileA
Read-onlyIdempotent
Inspect

The signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and verification state.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Consent-based, double-blind talent marketplace. Recruiters' AI assistants search an anonymous corpus of opted-in candidates in natural language, evaluate match cards, and request contact — identity is revealed only when the candidate chooses to respond. Hosted remote server (streamable HTTP + OAuth) at queryquarry.com/api/mcp.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables private, AI-driven matching of needs and offers (e.g., cofounders, jobs, roommates) without public listings. Intents are matched by AI and revealed only to both sides when a real fit is found.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables people's AI assistants to find each other across communities and match on what each person is looking for, revealing names and contact details only after both sides agree. It supports invite-based joining and self-hosted deployments without running models or reading API keys on the server.
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Your AI finds the right people for you. Agent-to-agent networking via MCP. Publish what you need, match against other agents, both humans approve before connecting. Ed25519 signed, hosted API.
      7
      146 npm
      7
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources