Skip to main content
Glama
omnara-ai

omnara

Official
by omnara-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

Update project model grant

grant_models_edit
Destructive

Update a project's overrides for its configured model; omitted fields keep current values, and null clears an override so the project inherits model settings. Changes apply on the next model call.

Instructions

Updates the project's overrides for the configured model. Omitted fields keep their current values; null clears an override so the project inherits from the configured model. The grant is live policy: agents already using the model re-apply the updated overrides on their next model call, against the configured-model revision each agent pinned at launch. Updates are validated against the configured model's current revision only, so an update can make an agent pinned to an older, incompatible revision fail its next model call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIDYes
projectIDYes
modelGrantIDYes
supports_toolsNoProject-level tool-use gate. Can disable tools, but cannot enable tools when the configured model does not support them.
input_modalitiesNoProject subset of configured-model input types.
max_output_tokensNoProject output-token ceiling. Cannot exceed the configured model's ceiling.
output_modalitiesNoProject subset of configured-model output types.
supports_reasoningNoProject-level reasoning gate. Can disable reasoning, but cannot enable reasoning when the configured model does not support it.
context_window_tokensNoProject context budget for input and output tokens. Cannot exceed the configured model's budget. Triggers compaction when estimated input exceeds the remaining budget after output and safety reserves. The turn fails if compaction cannot make it fit.
default_cache_retentionNo
default_reasoning_effortNoProject default reasoning effort.
default_max_output_tokensNoProject default per-request output-token cap.
supported_reasoning_effortsNoProject subset of configured-model reasoning efforts. If this excludes the inherited default_reasoning_effort, set default_reasoning_effort on the grant too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: omitted fields retain current values, null clears an override to inherit from the configured model, changes are live policy re-applied on each agent's next model call against its pinned revision, and updates are validated only against the current revision so older pinned agents can fail. This explains why the tool is flagged destructive and non-idempotent.

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?

Three sentences, purpose front-loaded, then the omitted/null contract, then the live-policy and revision-validation consequences. Every sentence adds distinct information an agent needs and none is padding.

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 13-parameter mutation with no output schema, the description covers the mutation contract, inheritance behavior, and the risk of breaking pinned agents. It omits auth/permission requirements and return shape, but the substantive calling-time risks are addressed.

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 only 69% across 13 parameters, so the description carries partial burden. It supplies the critical shared semantics that the schema lacks: omission preserves, null clears and reverts to inheritance, and grant-level values are constrained by the configured model's capabilities.

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 states a specific verb and resource: it 'updates the project's overrides for the configured model', and the omitted-field/null semantics make clear this edits an existing grant rather than creating one. It does not name grant_models_add or grant_models_delete as the alternatives, so sibling differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

The description explains what the tool does operationally but never states when to reach for it over grant_models_add, grant_models_delete, or grant_models_list. Usage is inferable from the update semantics, but no explicit when-to-use or when-not-to-use guidance is provided.

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

Deploy Server

Other Tools