mcpforwork

Overview Schema Source Related Servers Discussions Admin

submit_findings

Submit extracted job postings to dedupe, score against your profile, and persist them. Each entry requires at least a URL and title.

Instructions

Ingest postings YOU extracted from a source: deduped, scored against the profile, and persisted. Each finding needs at least url + title.

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": {
      "source_slug": "<source_slug>",
      "findings": "<findings>"
    },
    "name": "submit_findings"
  }
}

Input Schema

Name	Required	Description	Default
`findings`	Yes
`source_slug`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description discloses that the tool will dedupe, score against the profile, and persist the findings, giving a clear behavioral model. It also states a hard requirement for each finding (url + title). Since no annotations are provided, the description carries the full burden and does so adequately, though it omits error handling and permission requirements.

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 concise sentences with no filler. The main action is front-loaded ('Ingest'), and every phrase adds value, making it highly efficient.

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 with only two parameters, and the description covers the purpose, processing steps, and a key validation rule. An output schema exists, so return values are not needed. Minor gaps remain around prerequisites (e.g., source existence), but these are common sense for the domain.

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 description provides crucial semantic info for the 'findings' parameter by requiring at least url + title, which is not in the schema. The 'source_slug' parameter is implied by 'from a source', but not explicitly detailed. Given 0% schema coverage, this description partially compensates for the missing parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's verb ('Ingest') and resource ('postings/findings'), and explains the pipeline: deduped, scored, and persisted. The phrase 'YOU extracted' distinguishes it from URL-based import tools like import_from_url_findings, making the purpose specific and unambiguous.

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?

The description implies usage when the agent has already extracted postings from a source, as opposed to importing via URL. It provides clear context but does not explicitly name alternatives or state when not to use it, leaving some room for interpretation.

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