Skip to main content
Glama
Sign In
Bijon Portfolio MCP Server

Bijon Portfolio MCP Server

by Bijon2002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

getCertificates

Retrieve a list of professional and academic certifications earned by Bijon, including issuer names and completion dates.

Instructions

Get the list of professional and academic certifications earned by Bijon, including issuer names and completion dates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Since no annotations are provided, the description carries full burden for behavioral transparency. It correctly indicates this is a read operation (returns a list) and specifies the data scope (Bijon's certifications). It does not mention pagination, order, or what happens if no certifications exist, but for a simple, parameterless, single-person list, this is largely sufficient.

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?

One sentence that is perfectly front-loaded with the action and result. Every word earns its place; no fluff. Ideal for an AI agent to parse quickly.

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?

Given the tool has zero parameters, no output schema, and simple intent, the description is complete. Minor points like whether the list is sorted by date or name are not covered, but the core use case is fully addressed. Sibling tools are clearly distinct in topic.

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 schema description coverage is 100% (since there's nothing to cover). The description adds meaning by explaining what the output list contains (issuer names and completion dates), which the schema cannot convey. This exceeds the baseline expectation for a parameterless tool.

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 ('Get'), the resource ('list of certifications'), and the specific scope ('earned by Bijon'). It also mentions what information is returned ('issuer names and completion dates'), distinguishing it from sibling tools like getSkills or getProjects.

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?

The description implies the tool is for retrieving Bijon's certifications, but does not explicitly specify when to use this vs. alternatives like getSkills or getProfile. No discussion of when not to use it or prerequisites is provided.

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