Skip to main content
Glama
Portfolio MCP Server

Portfolio MCP Server

match_job_description

Read-onlyIdempotent

Ranks Ayush's projects against a pasted job description by scoring keyword overlap, so users can see which projects to review first.

Instructions

Rank Ayush's projects against a pasted job description.

Finds the technologies and topics in the text (LangGraph, FastAPI, RAG, agents, ...) and scores each project by how many it covers. This is a keyword overlap, a quick way to see which projects to open first. It is not an assessment of fit.

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_description": "<job_description>"
    },
    "name": "match_job_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNo
job_descriptionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower. The description still adds real behavioral context by disclosing the ranking method is keyword overlap and warning that results are not a fit assessment, which prevents over-trusting the output. It does not discuss tie-breaking, missing-keyword handling, or score behavior, leaving the mechanics partly opaque.

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?

Four short sentences, front-loaded with the action, then mechanism, then a usage framing, then a caveat. No filler; each sentence adds a distinct piece of information.

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?

With an output schema present, return-format detail is unnecessary, and the description plus annotations cover the safety and scope story well for a two-parameter read-only tool. The only real gap is the unexplained top_n parameter, which the agent must infer from its name and default.

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 0%, so the description must carry parameter meaning, and it does for the key one: 'a pasted job description' clarifies that job_description is raw text, not an ID or URL. However top_n is never mentioned, so the parameter that controls result size is left entirely undocumented.

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?

Names a specific verb and resource (rank projects against a job description) and explains the mechanism — extracting technologies/topics and scoring by keyword coverage. It also draws a clear scope boundary ('not an assessment of fit') that separates it from evaluation-style tools, though it never names a sibling such as search_projects_by_stack to contrast with.

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?

Gives concrete usage context — 'a quick way to see which projects to open first' — which tells the agent this is a triage step preceding detail lookups. The exclusion 'It is not an assessment of fit' is a useful when-not signal, but no explicit alternative tool is named for the cases this one can't serve.

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