Skip to main content
Glama
Sign In
adv2mcp

adv2mcp

Official
by Vodeninja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_prop_policy

Read-only

Retrieve the server's current allowed-prop profile before building or saving dupes; writes are blocked if no profile exists, so permissions aren't inferred from local installs or screenshots.

Instructions

Show the server allowed-prop profile, reloaded on each call. Missing profiles block writes. Never infer server permission from local installation or a screenshot.

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_prop_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds details beyond the read-only annotations: the profile is reloaded on every call, missing profiles block writes, and permission should not be inferred from local installs or screenshots. It does not cover auth or rate limits, but annotations already carry the safety profile.

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 short sentences, front-loaded with the core action, and each sentence adds a distinct operational point: freshness, write impact, and a safety warning.

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?

Given zero parameters, read-only annotations, and an output schema, the description covers freshness, write blocking, and permission-inference safety. No critical invocation detail 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?

There are zero parameters, so the baseline is 4 and the description need not compensate for schema gaps. It adds no parameter semantics because none exist.

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?

States a specific verb ('Show') and resource ('server allowed-prop profile'), with reload behavior distinguishing it from a cached status check. It does not explicitly name siblings, but none of the listed sibling tools overlap with policy inspection.

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?

Implies when to use it: before writes, because missing profiles block writes, and warns against inferring permission from local installation or screenshots. It does not name an alternative or a when-not condition, but the operational context is clear.

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