Foundaree

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, 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

TableJSON Schema

Name	Required	Description	Default
`username`	Yes	Username of the person, e.g. "maya-chen"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes
`total`	Yes
`people`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 27, 2026

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"
+}

Changed1 schema field changedSep 27, 2026
- addedOutput schema / properties / people / items / properties / updatedAt
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedSep 25, 2026

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"
+}

Changed1 schema field changedSep 23, 2026
- addedOutput schema / properties / people / items / properties / priceLine
```
Added value: +{
+  "maxLength": 200,
+  "type": "string"
+}
```

Changed1 schema field changedSep 22, 2026

changedOutput schema / properties / people / items / properties / verifiedBy / items / enum

Previous value: -[
-  "phone",
-  "github",
-  "google"
-]New value: +[
+  "phone",
+  "github",
+  "google",
+  "licence"
+]

Changed1 schema field changedSep 19, 2026
- addedOutput schema / properties / people / items / properties / foundareeRole
```
Added value: +{
+  "enum": [
+    "founder",
+    "team"
+  ],
+  "type": "string"
+}
```

Changed1 schema field changedSep 19, 2026

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"
+}

Changed1 schema field changedSep 19, 2026
- addedOutput schema / properties / people / items / properties / email
```
Added value: +{
+  "type": "string"
+}
```
First observedSep 19, 2026

TDQS

B3.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds genuine behavioral context beyond them: contact fields are returned only 'when the person made them public', licence data appears only 'once verified', and role assignment is Foundaree-controlled. These are useful disclosures, though they focus more on data semantics than on tool operation.

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?

The single purpose sentence is well front-loaded, but it is followed by an extremely dense run-on cataloguing dozens of output fields. Much of this duplicates the output schema, and the length makes it hard to extract the actionable part.

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?

The task is simple (one required param, read-only), and the description plus annotations plus output schema cover it fully, including the `success`/`found`/`person` result shape. If anything it is over-complete, since it re-explains return values the output schema already owns.

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% and there is a single `username` parameter already documented in the schema. The description adds no format, casing, or resolution guidance beyond what the schema provides, so the 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.' An agent can tell this is a targeted lookup rather than a search. It never explicitly names search_people as the alternative, so sibling differentiation is implied rather than stated.

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 when-to-use or when-not-to-use guidance is given. The description never contrasts this with search_people or explains that a username must already be known. Usage is only inferable from the required `username` parameter.

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

All Foundaree tools Inspect

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

Need Help?