Skip to main content
Glama
Sign In
Bijon Portfolio MCP Server

Bijon Portfolio MCP Server

by Bijon2002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getProjects

Retrieve portfolio projects, filtered by technology keyword like React or Python, to find relevant work examples.

Instructions

List Bijon's curated portfolio projects, optionally filtered by a tech stack keyword (e.g. React, Laravel, PHP, Python, Deep Learning).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getProjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
techNoTechnology keyword to filter by (case-insensitive, e.g. 'React', 'Laravel')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral traits. It indicates a read operation ('List') and a filtering capability, but lacks details on limits, pagination, data freshness, or authorization requirements. The disclosure is adequate for a simple list tool but not comprehensive.

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 a single sentence with no unnecessary words. The most important information ('List Bijon's curated portfolio projects') is front-loaded, and the filtering detail is added concisely.

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?

Given the tool's low complexity (one optional parameter, no output schema), the description covers the main action and filter. However, since no output schema exists, describing the return value (e.g., list of project names and details) would improve completeness for an agent.

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 description coverage is 100%—the schema already describes the 'tech' parameter. The tool description adds value by providing concrete examples (e.g., 'React, Laravel') and clarifying the context ('Bijon's curated portfolio'), which goes beyond the schema's description.

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 verb 'List' and the resource 'Bijon's curated portfolio projects', making the tool's purpose immediately obvious. It distinguishes from siblings like getProfile and getSkills by specifying 'projects' and the 'curated portfolio' context.

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 when to use (listing projects) and mentions optional filtering, providing clear context. However, it does not explicitly state when not to use this tool or suggest alternative sibling tools for different needs.

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