Skip to main content
Glama
Sign In
invokit-mcp

invokit-mcp

Official
by invok-it
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_app

Retrieve the full details of any app by providing its unique slug, so you can review and invoke it through the invokit API marketplace.

Instructions

Get full details for a specific app by its slug.

Args: slug: The app's unique identifier.

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_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It conveys that this is a read-only lookup ('Get full details'), but it does not mention how invalid or unknown slugs are handled, e.g., whether an error is raised or a null result is returned.

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 extremely concise, front-loads the main purpose, and uses a clear Args block for the single parameter. No unnecessary words or repetition.

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 lookup with an output schema, the description covers the core intent adequately. It lacks alternative routing and error-handling context, but these are not critical for a basic getter.

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 schema only provides the parameter title 'Slug' with no description. The description adds meaningful semantics by stating that slug is 'The app's unique identifier', which compensates for the 0% schema description coverage.

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

Purpose4/5

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

The description clearly states the action ('Get full details') and the resource ('a specific app'), with the input identifier ('by its slug'). It does not explicitly distinguish itself from sibling retrieval tools like get_tool or search_apps, so it misses the full top score.

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 phrase 'by its slug' implies that the agent should use this tool when it already has an app slug and needs full details. However, it gives no explicit guidance about when not to use it or when to prefer an alternative such as search_apps or get_tool.

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