GetMattered

Get Application Profile

getmattered_get_application_profile

Read-onlyIdempotent

Reads the answers saved for employer forms and the questions still open. Changes nothing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getmattered_get_application_profile"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`changed`	Yes	The input fields this call saved. Empty from getmattered_get_application_profile, which only reads.
`profile`	Yes	The saved answers employer forms are filled from, after this call. Field names are the API's camelCase twins of the inputs.
`setupStep`	No	Present while account setup is open: the first setup step.
`openQuestions`	Yes	Kept for existing clients, as an empty list. The answer text names the fields the user can add. Null when those details could not be read.
`missingRequiredForApply`	Yes	Profile fields employer forms can require that are empty. GetMattered fills address fields from the user's saved address and location. With gap filling on, it also fills an empty postal code. With gap filling off, a form that requires a postal code is not sent until the profile has one. An empty state or country never stops a form. The user adds each field once on the profile, not per application.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 8, 2026

changedOutput schema / properties / openQuestions / description

Previous value: -"Kept for existing clients and always an empty list. The answer text names the fields the user can add. Null when those details could not be read."New value: +"Kept for existing clients, as an empty list. The answer text names the fields the user can add. Null when those details could not be read."

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed1 schema field changedNov 8, 2026

changedOutput schema / properties / missingRequiredForApply / description

Previous value: -"Profile fields employer forms can require that are empty. GetMattered fills address fields from the user's saved address and location. With gap filling on, it also fills an empty postal code. With gap filling off, a form that requires a postal code is not sent until the profile has one. An empty state or country never stops a form. The user adds each field once on the profile. Never ask for them per application."New value: +"Profile fields employer forms can require that are empty. GetMattered fills address fields from the user's saved address and location. With gap filling on, it also fills an empty postal code. With gap filling off, a form that requires a postal code is not sent until the profile has one. An empty state or country never stops a form. The user adds each field once on the profile, not per application."

Changed3 schema fields changedNov 7, 2026

changedOutput schema / properties / missingRequiredForApply / description

Previous value: -"Fields employer forms require that are still empty. They are filled automatically while gap filling is on, and the user can add real values later."New value: +"Profile fields employer forms can require that are empty. GetMattered fills address fields from the user's saved address and location. With gap filling on, it also fills an empty postal code. With gap filling off, a form that requires a postal code is not sent until the profile has one. An empty state or country never stops a form. The user adds each field once on the profile. Never ask for them per application."

changedOutput schema / properties / openQuestions / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "applications": {
-          "type": "number"
-        },
-        "fact": {
-          "description": "The detail recent applications filled with a guess.",
-          "type": "string"
-        },
-        "lastSeenAt": {
-          "type": "string"
-        },
-        "setWith": {
-          "description": "The input fields that answer it. Empty when it is asked per application and cannot be preset.",
-          "items": {
-            "type": "string"
-          },
-          "type": "array"
-        }
-      },
-      "required": [
-        "fact",
-        "applications",
-        "lastSeenAt",
-        "setWith"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "applications": {
+          "type": "number"
+        },
+        "fact": {
+          "description": "A detail employer forms ask for.",
+          "type": "string"
+        },
+        "lastSeenAt": {
+          "type": "string"
+        },
+        "setWith": {
+          "description": "The input fields that hold it. Empty when it is asked per application and cannot be preset.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "fact",
+        "applications",
+        "lastSeenAt",
+        "setWith"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / openQuestions / description

Previous value: -"Details GetMattered guessed because the user never gave them. Null when they could not be read."New value: +"Kept for existing clients and always an empty list. The answer text names the fields the user can add. Null when those details could not be read."

Changed2 schema fields changedNov 6, 2026

changedOutput schema / properties / missingRequiredForApply / description

Previous value: -"Fields employer forms require that are still empty. Ask the user; never guess."New value: +"Fields employer forms require that are still empty. They are filled automatically while gap filling is on, and the user can add real values later."

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

AddedOct 25, 2026

TDQS

A3.5/5.0

Behavior2/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, and 'Changes nothing' merely restates the read-only hint rather than adding new behavioral context. Nothing is said about freshness, scope, or whether the profile is per-user or per-employer, so the sentence earns little beyond the structured fields.

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

Conciseness5/5

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

Two short sentences, front-loaded with what is read and followed immediately by the safety clarification. No filler or repetition of the title.

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 tool is simple (no params), an output schema exists so return values need no explanation, and the description conveys what content is returned. The only gap is the missing explicit contrast with the update sibling, which matters in such a large sibling set.

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?

The tool takes zero parameters, so the schema places no documentation burden on the description. Baseline for a no-parameter tool is 4, and nothing in the description muddies that.

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?

The description gives a concrete verb ('Reads') and a concrete resource ('the answers saved for employer forms and the questions still open'), which tells an agent what data comes back better than the bare name would. It does not name the sibling getmattered_update_application_profile, so the read/write pairing is only implicit, but the phrase 'Changes nothing' does signal the distinction.

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?

There is no explicit statement of when to call this instead of getmattered_update_application_profile or getmattered_get_profile; the usage is implied by 'Changes nothing' (pick this when you only want to inspect). No prerequisites or exclusions are stated, so an agent must infer the read-vs-write routing from the names.

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

All GetMattered 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.

Get Application Profile

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources