Skip to main content
Glama
Sign In
Bijon Portfolio MCP Server

Bijon Portfolio MCP Server

by Bijon2002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getGithubRepos

Retrieve a live list of GitHub repositories with updated stats, languages, and descriptions to showcase active portfolio projects for AI assistants.

Instructions

Fetches dynamic, live repository list of Bijon from GitHub, displaying updated repositories, languages, description, and stats.

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": "getGithubRepos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It says 'dynamic, live' suggesting real-time data and lists the displayed fields. However, it does not disclose whether authentication is required, rate limits, or data freshness guarantees. It provides moderate transparency for a simple read tool.

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 17-word sentence that immediately conveys the action and key outputs. It is tightly written with no filler or repetition, and it front-loads the purpose.

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?

For a tool with no parameters and no output schema, the description is fairly complete: it states the source (GitHub), the owner (Bijon), and the data included (repos, languages, description, stats). It could be improved by explicitly stating that it returns a list, but the current text covers the essentials.

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?

There are zero parameters, and the schema coverage is trivially 100%. The description does not add parameter info since none exist, so the baseline of 4 is appropriate. No additional semantics are needed.

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 'fetches' and the specific resource 'dynamic, live repository list of Bijon from GitHub'. It lists what is displayed (repositories, languages, description, stats), which distinguishes it from siblings that ask about Bijon, get profile, projects, skills, or certificates.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The name and description imply it's for GitHub repos, but there is no mention of when not to use it or scenarios where a sibling would be more appropriate. This is an adequate but not strong score given the sibling list.

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