Skip to main content
Glama
Sign In
mcpforwork

mcpforwork

by avivancos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

check_seen

Identify which URLs the copilot has already scouted or applied to, so you can focus on new job postings only.

Instructions

Report which URLs the copilot already knows (scouted or applied). Only browse/apply the ones marked 'new'.

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": {
      "urls": "<urls>"
    },
    "name": "check_seen"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It communicates the read-only nature by using 'Report,' but does not explicitly state side effects, permissions, or limitations. It adds context about 'scouted or applied' statuses, which is helpful, but more disclosure would be expected.

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?

The description is two sentences, front-loaded with the main action, followed by a clear actionable instruction. Every word earns its place, with no redundancy or fluff.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, output schema present), the description is complete. It tells the agent what the tool does and how to act on the results, providing sufficient context for invocation and follow-up.

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 schema has a single 'urls' parameter with no description, but the tool description clarifies that these are the URLs to check against known status. This adds meaning beyond the raw schema, compensating for the 0% schema description coverage.

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 function: 'Report which URLs the copilot already knows (scouted or applied).' It uses a specific verb (report) and resource (URLs), and distinguishes the tool by indicating it checks known status. It also adds a directive for follow-up actions, which clarifies purpose further.

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 provides clear usage context by instructing to 'Only browse/apply the ones marked new.' This implies the tool should be used before actions to filter URLs. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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

Deploy Server

Other Tools