Skip to main content
Glama

Shlok Bam's portfolio

Open-source contributions

get_open_source
Read-onlyIdempotent

Shlok's open-source contributions: his pull requests to other people's GitHub repositories, live from GitHub (cached up to 3 hours). Returns totals (merged, in review, closed, projects) and each repository (name, stars, description, link) with its pull requests (title, state, number, dates, link), merged work first. List submissions (awesome lists, portfolio directories) are left out. If GitHub can't be reached, the copy saved at the site's last build is returned with "source": "snapshot". Takes an optional status filter; no match returns empty lists. For his own projects use list_projects; for his own recent commits, get_activity.

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

Input Schema

NameRequiredDescriptionDefault
statusNoOnly pull requests in this state: "merged", "open" (still in review), "closed" (closed without merging), or "all".all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds important context beyond that: cached up to 3 hours, merged work ordered first, snapshot fallback with "source": "snapshot" when GitHub is unreachable, excluded submissions, and empty lists when no PR matches.

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 front-loaded with the resource and source, then covers returns, exclusions, fallback behavior, filtering, and alternatives. Every sentence contributes needed information, especially because there is no output schema.

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?

With no output schema, the description must explain what comes back, and it does: totals, repository details, PR fields, ordering, snapshot fallback, and exclusions. It is complete enough for an agent to invoke the tool correctly and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the enum already documents "merged", "open", "closed", and "all" in detail. The description adds only the no-match behavior, which is useful but limited beyond what the schema already provides.

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 states a specific resource and scope: Shlok's pull requests to other people's GitHub repositories, returned with repository and PR details. It also distinguishes the tool from list_projects and get_activity, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit routing: use list_projects for his own projects and get_activity for his own recent commits. It also excludes list submissions and explains the optional status filter, leaving little ambiguity about when to use this tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.