Skip to main content
Glama
Mipiti
by Mipiti

create_reliance

Declare a dependency from a consumer model to a provider control. In delegated mode, no local objective; in relied_upon mode, consumer control depends on provider.

Instructions

Declare a cross-model dependency: this model relies on a provider control.

Two modes (the target is ALWAYS a provider control — credit terminates at a proven mechanism):

  • delegated: this model does NOT implement an objective locally; it is handled entirely by the provider's control. Pass source_objective_id.

  • relied_upon: this model has its OWN control whose validity depends on the provider's control. Pass source_control_id.

The provider must be a model in the SAME workspace as the consumer (reliance is workspace-scoped and does not reach across workspace boundaries). The edge enters draft and runs LLM semantic validation; it carries no credit until confirmed via confirm_reliance (and only when validation returned valid). Returns the created edge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes"delegated" or "relied_upon".
model_idYesthe consumer model declaring the dependency.
server_versionYes
provider_model_idYesthe model whose control satisfies the dependency.
source_control_idNoconsumer control id (required for "relied_upon").
provider_control_idYesthe provider's control (the credit terminus).
source_objective_idNoconsumer objective id (required for "delegated").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavioral details: the edge enters draft state, undergoes LLM semantic validation, and carries no credit until confirmed via 'confirm_reliance' and only if validation returns 'valid'. It also clarifies that credit terminates at a proven mechanism.

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 description is structured in three clear paragraphs: overview, mode details, and behavioral context. While it is somewhat lengthy, each sentence serves a purpose and the core message is front-loaded.

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?

Given the tool's complexity (7 parameters, 5 required, output schema exists), the description covers purpose, modes, workspace scoping, draft/validation flow, and confirmation dependency. It lacks mention of error handling or prerequisites, but overall it is comprehensive enough for an agent to use correctly.

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 has high coverage (86%), but the description adds significant value by explaining the mode-dependent parameters and their relationship. It clarifies when 'source_control_id' vs 'source_objective_id' is required, which is not evident from the schema alone.

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 clearly states the tool's purpose: to declare a cross-model dependency (reliance) between a consumer and a provider control. It specifies two distinct modes ('delegated' and 'relied_upon'), differentiating it from siblings like 'confirm_reliance' and 'delete_reliance'.

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 description provides explicit guidance on when to use each mode, including which parameters to pass (source_objective_id for delegated, source_control_id for relied_upon). It also notes workspace-scoping and that the edge enters draft and requires confirmation. However, it does not explicitly state when not to use the tool or list alternatives.

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/Mipiti/mipiti-mcp'

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