Skip to main content
Glama

model_instance_get

Retrieve details of a specific Kaggle model instance by providing owner, model slug, framework, and instance slug.

Instructions

Get details of a specific model instance.

    Args:
        owner: Model owner username.
        model_slug: Model slug/name.
        framework: Framework name (e.g. 'tensorflow2', 'pytorch', 'jax').
        instance_slug: Instance slug identifier.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYes
model_slugYes
frameworkYes
instance_slugYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Lacks annotations, but the description implies a safe read operation. However, no additional behavioral traits (e.g., authentication, response format) are disclosed.

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?

Highly concise: purpose stated upfront, followed by a clear parameter list. Every sentence adds value without redundancy.

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?

Does not explain the role of model_instance relative to model, or why all four parameters are needed. With zero schema coverage, more context is necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description only repeats parameter names with minimal context (e.g., 'Model owner username.'). No additional meaning or constraints beyond schema.

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 uses a clear verb 'get' and specific resource 'details of a specific model instance', distinguishing it from sibling tools like model_get and model_instances_list.

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?

No guidance on when to use this tool over alternatives like model_get or model_instances_list, and no exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Galaxy-Dawn/kaggle-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server