Skip to main content
Glama
Sign In

Foundaree

by io.github.shujahmhd
OverviewDiscussionsAdmin

Get a person profile

get_person
Read-onlyIdempotent

Retrieve the full public profile for a username, including skills, experiences, projects, services (what they offer with prices: name, price in whole currency units or null for "ask", currency, per job/hour/day/visit/session/month for services or kg/litre/piece/dozen/bunch/packet/plate for products, from = starting price, note), licence (a registration number Foundaree's admin looked up on its public register, e.g. a doctor's NMC number: body, number, checkedAt; only once verified, and then "licence" is also in verifiedBy), and the phone, WhatsApp and contact email (phone, whatsapp, contactEmail) when the person made them public. workProof, when at least one kind is proven, is a count, not a score: "Proof: proven of total" over GitHub, website and LinkedIn (LinkedIn has no proof yet), with the facts of each proven one: github (public facts of a GitHub account they proved is theirs by signing in with it: repos, stars, followers, top languages, last push, and when Foundaree read them) and website (their website links back to this profile). person.updatedAt is when they last edited the profile. Returns structured JSON with success, found and person fields. Each answer has two views: the text content is the JSON described above, and the structured content is a profile-card list (people, total, query). In apps that support MCP Apps (ChatGPT, Claude) the cards render as Foundaree profile cards. A person with foundareeRole ("founder" or "team") is part of Foundaree's own team; only Foundaree sets it.

Input Schema

NameRequiredDescriptionDefault
usernameYesUsername of the person, e.g. "maya-chen"

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
peopleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / people / items / properties / backed
      Added value: +{
+  "items": {
+    "maxLength": 160,
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}
    • addedOutput schema / properties / people / items / properties / workProof / properties / github / properties / languageRepos
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "repos": {
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "name",
+      "repos"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / people / items / properties / workProof / properties / github / properties / topics
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "repos": {
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "name",
+      "repos"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedOutput schema / properties / people / items / properties / updatedAt
      Added value: +{
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedOutput schema / properties / people / items / properties / languages
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
    • addedOutput schema / properties / people / items / properties / serviceAreas
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
  4. Changed1 schema field changed
    • addedOutput schema / properties / people / items / properties / priceLine
      Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
  5. Changed1 schema field changed
    • changedOutput schema / properties / people / items / properties / verifiedBy / items / enum
      Previous value: -[
-  "phone",
-  "github",
-  "google"
-]New value: +[
+  "phone",
+  "github",
+  "google",
+  "licence"
+]
  6. Changed1 schema field changed
    • addedOutput schema / properties / people / items / properties / foundareeRole
      Added value: +{
+  "enum": [
+    "founder",
+    "team"
+  ],
+  "type": "string"
+}
  7. Changed1 schema field changed
    • addedOutput schema / properties / people / items / properties / workProof
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "github": {
+      "additionalProperties": false,
+      "properties": {
+        "fetchedAt": {
+          "type": "string"
+        },
+        "followers": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "languages": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "lastPushAt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "login": {
+          "type": "string"
+        },
+        "publicRepos": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "stars": {
+          "maximum": 9007199254740991,
+          "minimum": 0,
+          "type": "integer"
+        },
+        "url": {
+          "format": "uri",
+          "type": "string"
+        }
+      },
+      "required": [
+        "login",
+        "url",
+        "publicRepos",
+        "followers",
+        "stars",
+        "languages",
+        "lastPushAt",
+        "fetchedAt"
+      ],
+      "type": "object"
+    },
+    "proven": {
+      "maximum": 9007199254740991,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "total": {
+      "maximum": 9007199254740991,
+      "minimum": 1,
+      "type": "integer"
+    },
+    "website": {
+      "additionalProperties": false,
+      "properties": {
+        "host": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        },
+        "verifiedAt": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "url",
+        "host",
+        "verifiedAt"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "proven",
+    "total"
+  ],
+  "type": "object"
+}
  8. Changed1 schema field changed
    • addedOutput schema / properties / people / items / properties / email
      Added value: +{
+  "type": "string"
+}
  9. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description does add real behavioral context: conditional field population (`licence` only once verified, contact fields only when made public), the two response views (text JSON vs structured profile-card list) and MCP Apps rendering. However it spends most of its length on data-shape exposition rather than call behavior, and never states what an error or a missing username path looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense paragraph that crams in exhaustive output-field documentation (services, licence, workProof, GitHub facts, updatedAt) via nested backticked terms. The purpose is front-loaded, but an output schema exists, so most of this volume restates structured data and buries the one operationally important line (the two response views) mid-paragraph.

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 a single-param, read-only lookup with an output schema and full annotation coverage, the definition leaves nothing critical unanswered about what the call does or returns. The only gap is the absence of a not-found/error description beyond the `found` flag, which is minor here.

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 coverage is 100% with a single required `username` carrying its own example, so the schema does the work. The description only restates "for a username" and adds nothing about format, casing or normalization (e.g. whether "Maya-Chen" resolves to "maya-chen"). 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?

Opens with a specific verb+resource ("Retrieve the full public profile for a username") and enumerates what the profile contains, so the agent knows exactly what it gets back. It stops short of naming how it differs from siblings like search_people, find or match_people, which also surface people.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this versus search_people, find, match_people or get. The requirement for an exact username is only implicit in the schema. An agent must infer that this is the full-profile-by-handle path while search_people is the discovery path.

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

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