Skip to main content
Glama
Sign In
agent-bridge

agent-bridge

by merlinh0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_model_policy

Retrieve current model policy rules, including allowed model glob patterns and tier overrides, to verify which models agents may use or which model is pinned to each tier.

Instructions

Current model rules.

allowed_models: glob patterns of the models agents may use; empty means every available model. tiers: the model pinned to a tier, where the automatic pick was overridden.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_model_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does disclose the shape and semantics of the returned policy — including the meaningful 'empty means every available model' rule and the meaning of an overridden tier. It does not state read-only nature, auth needs, or defaults beyond those two fields, so it is helpful but not fully transparent.

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?

Two short blocks with no filler: the scope statement first, then a compact glossary of the two returned fields. Every sentence conveys information an agent would otherwise have to discover from the output.

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?

Because there is no output schema, the description must explain the return value, and it does so for both documented fields. A brief note on what an empty tiers map or an unset policy means would close the remaining gap, but the essential semantics are present for a simple, parameterless read.

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 tool takes zero parameters, so there is no parameter semantics to carry; the baseline for a 0-param tool applies. The field definitions provided instead describe the response, which is a bonus rather than a substitute.

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 opening line 'Current model rules' plus the two field definitions make the resource concrete: this returns the active model policy (allowed model globs and per-tier pinned models). It is clearly a read of the current policy rather than a mutation, which implicitly separates it from set_model_policy, though it never names that sibling.

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 explicit when-to-use guidance and no alternatives referenced. An agent must infer that this is the read companion to set_model_policy and that it should be called before inspecting or changing model constraints; nothing in the text says so.

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