Skip to main content
Glama
Sign In

GetMattered

by com.getmattered
OverviewDiscussionsAdmin

Remove Saved Matches

getmattered_unsave_matches
Idempotent

Removes matches from the saved list. They stay in the user's matches.

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

Input Schema

NameRequiredDescriptionDefault
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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, but the description adds real value by explaining what is actually affected: only the saved-list membership is removed, while the match itself persists in the user's matches. That is exactly the distinction an agent needs before invoking a non-destructive mutation, though nothing is said about whether unsaving a non-saved id errors or is a silent no-op.

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

Conciseness4/5

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

Two short sentences with the action front-loaded and zero filler. The follow-up sentence is slightly ambiguous in wording ('They stay in the user's matches'), which takes a moment to parse but still earns its place by preventing a wrong mental model of the effect.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter batch mutation with full schema coverage, an output schema, and annotations covering safety and idempotency, the essentials are present. The remaining gap is routing: with closely related siblings such as getmattered_save_matches, getmattered_restore_matches, and getmattered_skip_matches, the description should say which one to reach for.

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 description coverage is 100% and the single parameter is well documented in the schema, including its source (getmattered_get_matches), the 1-to-25 batch bound, and an example. The description adds no parameter-level meaning, 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?

The description states a specific verb and resource ('Removes matches from the saved list') and the second sentence clarifies the scope of removal. It implicitly separates this from siblings like getmattered_save_matches and getmattered_restore_matches, though it never names them.

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 only implied: the reader must infer this is the inverse of saving and distinct from skipping or rejecting. There is no explicit when-to-use guidance, no mention of when to prefer getmattered_restore_matches or getmattered_skip_matches, and no stated preconditions such as the matches having been previously saved.

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