Farrukh Inomov

Projects

list_projects

Read-onlyIdempotent

All projects with tagline, stack, year and links. Use get_project with a slug for the details.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the answer: "de" for German or "en" for English.	en

Output Schema

Name	Required	Description	Default
`projects`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully carried by structured data. The description adds the shape of each returned entry (tagline, stack, year, links), which is useful but partly redundant with the existing output schema, and says nothing about pagination or result size.

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?

Two short sentences, no filler: the first describes content, the second redirects to the sibling. The content statement is front-loaded, which is the right order for a list tool.

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 simple one-parameter list tool with annotations and an output schema, this is nearly complete. The only omission is any note on result volume or whether the list is bounded, which a caller of an unfiltered list endpoint might want.

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?

There is a single optional parameter, lang, with an enum and 100% schema description coverage, so the schema fully explains it. The description adds no meaning beyond that, which is the expected baseline for fully documented parameters.

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 the resource (projects) and scope (all) and enumerates what each entry carries: tagline, stack, year and links. It also names the sibling get_project as the detail-oriented alternative, so an agent can tell the two apart without opening either schema.

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

Usage Guidelines4/5

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

"Use get_project with a slug for the details" explicitly routes detail lookups to the sibling tool, implying this one is for a broad overview. It stops short of stating when-not to call it (e.g. no pagination or result-count limits) but the primary fork is covered.

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

All Farrukh Inomov tools Inspect

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.