Skip to main content
Glama
Sign In
peerkith-mcp

peerkith-mcp

by BGarofalo1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

showcase_get

Retrieves the /showcase.json join showcase payload for MCP clients to inspect available showcases before verifying hires or posting fields.

Instructions

GET join showcase path (/showcase.json)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only HTTP GET and names the path, but discloses nothing about auth requirements, rate limits, caching, or failure modes for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from under-specification rather than efficiency. The single cryptic phrase "GET join showcase path" is not front-loaded with a clear verb+resource statement, so every word fails to earn an informational place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param tool with no output schema, the description should at least say what /showcase.json returns or when it is the right call among the many *_get siblings. Neither is present, leaving the agent with only a raw path.

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?

The tool takes no parameters, so the schema and description agree that there is nothing to document. Baseline 4 applies for a zero-parameter tool; the description adds no parameter information because none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"GET join showcase path (/showcase.json)" largely restates the tool name (showcase_get) and adds only a literal endpoint path. The odd phrasing "join showcase path" leaves the resource and what is actually fetched ambiguous, so an agent cannot confidently distinguish its purpose from show_case-like siblings such as wall_get or trail_get.

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

Usage Guidelines2/5

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

The description offers no when-to-use, when-not-to-use, or alternative routing. With ten sibling tools including other *_get endpoints (pending_get, wall_get, trail_get, llms_get), there is no signal about which situation selects showcase_get.

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