Nanites

Create Profile

create_profile

Creates a named profile for delegating bounded tasks to local or cheap cloud models, with optional specs, endpoint, pricing, test plan, notifications; concurrency derived from specs via guardrail tiers.

Instructions

Create a named profile. Machine specs, endpoint, pricing, test_plan_ref and ntfy are optional and resolve to documented defaults; concurrency is derived from machine specs via the guardrail tiers.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`ntfy`	No
`tools`	No
`pricing`	No
`endpoint`	No
`use_case`	No
`inference`	No
`dynamic_model`	No
`machine_specs`	No
`test_plan_ref`	No
`vision_capable`	No
`concurrency_override`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description must disclose behavior itself; it does add value by stating that optional fields resolve to documented defaults and that concurrency is derived via guardrail tiers. However, it omits effects such as duplicate-name handling, persistence, whether the new profile becomes active, and whether an override can bypass the guardrail derivation.

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?

The two sentences are compact and front-loaded with the core purpose before the defaults note. Minor deduction for being too terse relative to the 12-parameter nested schema, though every included clause carries meaning.

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?

Despite a large nested schema, no output schema, and no annotations, the description leaves important context uncovered: tool routing, effects of creation, key parameter meanings, and the relationship between concurrency_override and derived concurrency. An agent can call it with only the required name but would be guessing on most optional fields.

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 description coverage is 0%, so the description must compensate, but it names only 5 of 12 parameters and omits major ones such as tools, inference, use_case, dynamic_model, and vision_capable. It adds useful semantics for the listed fields, but the unlisted parameters remain unexplained and concurrency_override is not reconciled with the statement that concurrency is derived from machine specs.

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 uses a specific verb ('Create') and resource ('a named profile'), and the emphasis on name aligns with the schema's only required field. It does not explicitly distinguish itself from update_profile or switch_profile, but the creation semantics are unambiguous enough to avoid confusion.

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?

There is no guidance on when to choose this tool over update_profile, switch_profile, or list_profiles, and no conditions or prerequisites are stated. The only usage-related information is that several fields are optional and fall back to defaults, which is more parameter behavior than routing guidance.

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

Deploy Server