Skip to main content
Glama

Smarty Pants

Request a model

request_model
Idempotent

Ask Smarty Pants to host a model that is not offered yet. Best with a Hugging Face link or org/name id. We check it at once (license, safe file types, no outside code, fits our Macs) and give you a track link to follow it from requested to checked, in testing and live. Nothing is downloaded or charged. No sign-in needed.

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": {
      "model": "<model>"
    },
    "name": "request_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: what you would use it for
modelYesA Hugging Face or OpenRouter link, an org/name id, or a model name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the annotations by disclosing exactly what happens after submission: immediate checks for license, safe file types, no outside code, and fit for their hardware, plus a track link with lifecycle stages. It also resolves the questions annotations can't answer — nothing is downloaded or charged and no sign-in is required.

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-loads the purpose in the first sentence and then layers input preference, processing, and outcome in a logical sequence. The parenthetical checklist is dense but earns its place; a slightly tighter phrasing would reach the top score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter submission tool with no output schema, the description covers what is required, what happens on submit, what the caller receives (a track link), and the cost/auth posture. Nothing needed to call it correctly is missing.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds a preference ordering for the model parameter ('best with a Hugging Face link or org/name id') that the schema does not express. The optional note parameter is left unmentioned, but the schema documents it adequately.

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 — asking the service to host a model that is not offered yet — which cleanly separates it from lookup siblings like find_model and list_models. An agent knows immediately this is a submission action, not a search.

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?

The phrase 'a model that is not offered yet' implicitly scopes usage against discovery tools, and it names the best input forms (Hugging Face link, org/name id). It does not explicitly name an alternative tool or state when not to submit, so it falls short of full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources