Skip to main content
Glama
Sign In

GetMattered

by com.getmattered
OverviewDiscussionsAdmin

Skip Job Matches

getmattered_skip_matches
Idempotent

Skips matches the user does not want, with an optional reason that improves later matches. Nothing is sent or spent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_match_ids": "<job_match_ids>"
    },
    "name": "getmattered_skip_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy the user skipped them, so the matcher learns (e.g. "too_senior").
job_match_idsYesJob match ids from getmattered_get_matches, 1 to 25 (e.g. [48213, 48214]).

Output Schema

NameRequiredDescriptionDefault
actionYesThe operation that ran, one of save, skip, unsave or restore.
resultsYes
attemptedYes
setupStepNoPresent while account setup is open: the first setup step.
succeededYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / action / description
      Previous value: -"The operation that ran: save, skip, unsave or restore."New value: +"The operation that ran, one of save, skip, unsave or restore."
    • 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."
  2. Changed1 schema field changed
    • addedOutput schema / properties / setupStep
      Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the description's main job is added context. 'Nothing is sent or spent' usefully rules out emails to employers and credit consumption, and 'improves later matches' discloses the matcher-learning side effect — both are facts not present in annotations or schema.

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 compact sentences, with the action and its scope front-loaded and the reassurance clause last. No filler or restated field names.

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 (one required id array, one optional enum) and an output schema exists, so return values need no explanation. What is missing is the recovery path — that skipped matches can be restored — which matters for a mutating tool, but the 'nothing is sent or spent' line covers the main risk concern.

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 coverage is 100% with an enumerated reason field, so baseline is 3. The description earns above baseline by explaining why the optional reason should be supplied (it improves future matches), adding intent that the enum's per-value description does not convey.

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?

States a specific verb and resource ('Skips matches the user does not want') and adds the reason parameter's effect, so an agent knows this is the skip/dismiss operation among the match family. It does not name the inverse sibling (getmattered_restore_matches) or otherwise differentiate itself from save/unsave, which keeps it short of a 5.

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?

Usage is implied by 'matches the user does not want' — call it when the user rejects a match. There is no explicit when-not guidance, no mention of how to undo (restore_matches), and no statement of prerequisites such as needing ids from getmattered_get_matches, which the schema carries instead.

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

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