Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Register Model

register_model

Registers a Hugging Face model for serving and returns a registration_id used by deploy_serving; the model downloads only at deployment, and repeated registrations reuse the existing record.

Instructions

Register a Hugging Face model for serving and return its registration_id for deploy_serving. It costs nothing: the model downloads only when deployed. Run detect_model first; registering the same repo again returns the existing registration. Leave framework out: text models run on vllm, and sglang is refused. hf_token_id (from source_credentials) is for private repos. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "huggingface_repo": "<huggingface_repo>"
    },
    "name": "register_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
frameworkNo
workspaceNo
hf_token_idNo
operation_idNo
context_lengthNo
huggingface_repoYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the operation is free (download deferred to deploy), duplicate repos return the existing registration, sglang is rejected, and a full operation_id retry protocol is spelled out. One tension: the dedup statement ("registering the same repo again returns the existing registration") reads as idempotent-resource behavior while `idempotentHint` is false — likely because each attempt is a new operation, but the description does not reconcile the two.

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 purpose and return value, then cost, prerequisite, parameter rules, and the write-protocol block in a logical order. The `operation_id` paragraph is boilerplate but load-bearing; only the cost/prerequisite sentences could be tightened slightly.

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 7-parameter mutating tool with an output schema, the description covers the risky parts — cost, dedup, framework restriction, token scoping, and timeout/retry handling — so an agent can invoke it safely. The remaining gap is the unexplained `name`, `workspace`, and `context_length` parameters.

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 0%, so the description carries the full burden, and it only covers part of it: `framework` (vllm default, sglang refused), `hf_token_id` (private repos, from `source_credentials`), and `operation_id` (UUID generation, reuse, retry semantics) are explained well. `name`, `workspace`, and `context_length` carry no meaning in either the schema or the description, leaving three of seven parameters opaque.

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 ("Register a Hugging Face model for serving") plus the return value (`registration_id`) and its consumer (`deploy_serving`). An agent can distinguish this from `detect_model`, `deploy_serving`, and `delete_model` without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete routing: run `detect_model` first, leave `framework` out because sglang is refused, take `hf_token_id` from `source_credentials` for private repos, and use `operation_status` after timeouts. Prerequisites, parameter-level when-to-use rules, and recovery alternatives are all named rather than implied.

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