Skip to main content
Glama
Sign In
terminal-love-mcp

terminal-love-mcp

by jpoindexter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Get tool details

get_tool

Get comprehensive details for a CLI/TUI tool from Terminal Trove by specifying its slug, returning metadata like description, GitHub, install commands, and screenshots.

Instructions

Full Terminal Trove details for a tool: description, GitHub, language, license, platforms, tags, install commands, and screenshot URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYestool slug, e.g. 'lazygit'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 full responsibility. It lists return fields but does not disclose safety, side effects, authentication needs, or rate limits. For a read operation, minimal behavioral context is given.

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 a single sentence that front-loads the purpose and enumerates return fields. Every word is necessary; no wasted content.

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 one parameter and no output schema, the description adequately covers what the tool returns by listing fields. It could mention it's a read operation, but overall sufficient for its simplicity.

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 coverage is 100%, with one parameter 'slug' described in schema. The description does not add parameter-specific meaning beyond listing return fields, so baseline 3 is appropriate.

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 title 'Get tool details' and description clearly state the tool retrieves full details for a specific tool, listing specific fields. It distinguishes from siblings like browse_category or list_categories by focusing on a single tool's details.

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 use when you need details of a specific tool, but provides no explicit guidance on when not to use or alternatives. With many sibling tools, usage context is only implicit.

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