goldseam

Search Certifications

search_certifications

Read-only

Which certification is this prose name? Start here for any plain question — a trade, field, job, skill, or company in everyday words. Returns candidates with ids, issuers, and source basis — candidates rather than a single guess when the name is ambiguous; the ids feed the other certification tools.

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": {
      "query": "<query>"
    },
    "name": "search_certifications"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional page size (default 20, at most 50)
`query`	Yes	What you are looking for, in everyday words — a trade, field, job, or company
`issuer`	No	Optional: only certifications from this organization
`offset`	No	Optional: the next_offset from a previous answer

Output Schema

Name	Required	Description
`contract`	Yes
`statement`	No
`portal_url`	No	The same search on the portal
`understood`	No	What was read: words, issuer, and match (step, matched_terms, statement)
`next_offset`	No
`next_actions`	No
`certifications`	No	The certification cards
`total_matching`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "certifications": {
+      "description": "The certification cards",
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "next_actions": {
+            "items": {
+              "properties": {
+                "arguments": {
+                  "type": "object"
+                },
+                "label": {
+                  "type": "string"
+                },
+                "tool": {
+                  "description": "A GoldSeam service",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "label",
+                "tool",
+                "arguments"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "contract": {
+      "type": "string"
+    },
+    "next_actions": {
+      "items": {
+        "properties": {
+          "arguments": {
+            "type": "object"
+          },
+          "label": {
+            "type": "string"
+          },
+          "tool": {
+            "description": "A GoldSeam service",
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "tool",
+          "arguments"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_offset": {
+      "type": "integer"
+    },
+    "portal_url": {
+      "description": "The same search on the portal",
+      "type": "string"
+    },
+    "statement": {
+      "type": "string"
+    },
+    "total_matching": {
+      "type": "integer"
+    },
+    "understood": {
+      "description": "What was read: words, issuer, and match (step, matched_terms, statement)",
+      "type": "object"
+    }
+  },
+  "required": [
+    "contract"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 10, 2026

changedInput schema / properties / limit / description

Previous value: -"Optional maximum number of candidates"New value: +"Optional page size (default 20, at most 50)"

addedInput schema / properties / offset

Added value: +{
+  "description": "Optional: the next_offset from a previous answer",
+  "type": "integer"
+}

Changed3 schema fields changedSep 10, 2026

changedInput schema / properties / issuer / description

Previous value: -"Optional issuer name to narrow candidates"New value: +"Optional: only certifications from this organization"

changedInput schema / properties / query / description

Previous value: -"Prose name, exam code, or issuer string to resolve"New value: +"What you are looking for, in everyday words — a trade, field, job, or company"

addedInput schema / properties / query / examples

Added value: +[
+  "nursing",
+  "HVAC",
+  "welding",
+  "IBM",
+  "project management"
+]

First observedSep 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

readOnlyHint=true already covers safety, so the description's added value is the disclosure that it returns multiple candidates rather than one guess when ambiguous, plus what each candidate contains (ids, issuers, source basis). This is meaningful behavioral context beyond the annotation.

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?

Front-loads the central question and keeps to a few tight sentences. There is minor redundancy in restating the 'trade, field, job, company' list that also appears in the schema examples, but overall it is well-structured.

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?

An output schema exists so return values needn't be re-explained, and the description still usefully previews candidate shape and the id hand-off to other tools. Adequate for a 4-param search/resolution tool.

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%, so all four parameters (including limit default/max, issuer, offset) are already documented in the schema. The description's 'everyday words' framing reinforces the query parameter but adds no syntax or format detail beyond the schema.

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?

Frames the tool as a name-resolution step ('Which certification is this prose name?'), which cleanly distinguishes it from get_certification (lookup by id) and by-occupation siblings. It states the resource and the operation, though it doesn't name a specific sibling to avoid.

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

Usage Guidelines4/5

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

Explicitly says to 'start here for any plain question' and enumerates the everyday-word inputs it accepts, and notes the returned ids 'feed the other certification tools.' That routes the agent well, but there is no explicit when-not or negative case.

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

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