Skip to main content
Glama
Sign In

saagarpatel.dev Portfolio

by io.github.saagpatel
OverviewDiscussionsAdmin

Play a portfolio demo

play_demo
Read-only

Play one of the site's interactive demos, rebuilt from the public corpus pages that fully describe them. "interleaving": the Interleaving Explorer, two writers on one database row, six schedules, warn vs enforce mode, and the lost update with its receipts. "failure-museum": match each Agent Failure Museum exhibit (synthetic failures) to the control that catches it. Hosts that support MCP Apps render it as an interactive view; others get the same data as 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": "play_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNoWhich demo: "interleaving" (default) or "failure-museum"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely useful behavior beyond that: hosts with MCP Apps get an interactive view while others receive the same data as JSON, and the failure-museum exhibits are flagged as synthetic. It does not discuss result size or any limits, which keeps it from a 5.

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

Conciseness4/5

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

Front-loaded with the core action, then demo specifics, then transport behavior — a sensible ordering. The quoted demo identifiers read a bit list-like and the interleaving clause is dense, but no sentence is wasted.

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?

With no output schema, the description correctly takes on the job of explaining what comes back (interactive view vs JSON), which is the key unknown for this tool. For a single optional enum parameter with full schema coverage, little else is needed.

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 coverage is 100% and the enum already documents both values, so the baseline is 3. The description goes further by explaining what each demo actually exercises (two writers on one row, six schedules, warn vs enforce, lost update), which helps an agent choose the right enum value.

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?

States a specific verb and resource ("Play one of the site's interactive demos") and enumerates the two available demos by name, with concrete content for each. No sibling tool overlaps with this, and an agent can tell instantly what this tool is for.

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?

Usage is implied by the topic descriptions of each demo (interleaving = concurrency schedules; failure-museum = matching failures to controls), so an agent can infer which value to pick. However, there is no explicit statement of when to reach for this versus other corpus/project tools, and no exclusion guidance.

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

All saagarpatel.dev Portfolio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources