validoria-mcp

Update Team Settings

update_team_settings

Update team configuration. All fields are optional — only provided fields are changed. Covers: AI enrichment (model, temperature, auto-enrich, spending cap), uptime (timeout, thresholds), severity escalation (recurrence/age triggers), run policies (concurrency, timeouts), SEO (rank tracking, keyword strategy), notification coalescing (digest), and the kill switch (testsPaused).

Input Schema

TableJSON Schema

Name	Required	Description
`aiModel`	No	Model id on the AI gateway for finding enrichment (e.g. mistral/mistral-small-2603, an EU route)
`aiEnabled`	No	Enable/disable AI finding enrichment
`aiCapAction`	No	Action when cap is reached
`testsPaused`	No	Kill switch — pauses ALL scheduled and manual test runs
`aiAutoEnrich`	No	Auto-enrich new findings with AI
`digestEnabled`	No	Enable notification alert coalescing
`aiMonthlyCapUsd`	No	Monthly AI spending cap in USD (null = unlimited)
`aiSourceReviewModel`	No	Model for AI source review plugin
`defaultRunTimeoutMs`	No	Default run timeout in ms
`digestWindowSeconds`	No	Digest window duration in seconds
`escalateInfoAgeDays`	No	Finding age in days before INFO→WARNING
`seoRankCheckEnabled`	No	Enable Google rank tracking
`uptimeFailThreshold`	No	Consecutive failures before DOWN
`uptimePingTimeoutMs`	No	Uptime ping timeout in ms
`maxDailyRunsPerTarget`	No	Max test runs per target per day (0=unlimited). Prevents overwhelming hosted sites with limited request budgets.
`escalateInfoRecurrence`	No	Finding recurrences before INFO→WARNING
`escalateWarningAgeDays`	No	Finding age in days before WARNING→CRITICAL
`defaultScheduleMultiplier`	No	Schedule frequency multiplier (< 1 = more frequent)
`escalateWarningRecurrence`	No	Finding recurrences before WARNING→CRITICAL
`uptimeDegradedThresholdMs`	No	Response time threshold for DEGRADED status
`maxConcurrentRunsPerTarget`	No	Max concurrent test runs per target

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 4, 2026

changedInput schema / properties / aiModel / description

Previous value: -"OpenAI model for finding enrichment (e.g. gpt-4o-mini)"New value: +"Model id on the AI gateway for finding enrichment (e.g. mistral/mistral-small-2603, an EU route)"

Changed1 schema field changedAug 20, 2026

addedInput schema / properties / maxDailyRunsPerTarget

Added value: +{
+  "description": "Max test runs per target per day (0=unlimited). Prevents overwhelming hosted sites with limited request budgets.",
+  "maximum": 1000,
+  "minimum": 0,
+  "type": "number"
+}

First observedAug 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior — patch semantics (only supplied fields change) and that testsPaused is a kill switch pausing ALL scheduled and manual runs — but omits permissions needed, reversibility, and the effect of unprovided fields on related settings.

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?

Front-loads the purpose and the key partial-update rule in the first two sentences, then lists the covered domains compactly. The enumeration is long but scannable and every clause maps to real parameters.

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 21-parameter mutation with no annotations and no output schema, the description covers the two things an agent most needs: that unspecified fields are untouched and which functional groups the parameters belong to. Missing only permission requirements and return behavior, which is partially mitigated by the get_team_settings sibling.

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 description coverage is 100%, so the baseline is 3, but the description adds genuine value by grouping the 21 parameters into named domains (AI, uptime, escalation, run policy, SEO, digest, kill switch), which helps an agent navigate a large flat schema.

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+resource ('Update team configuration') and enumerates the functional areas touched (AI enrichment, uptime, escalation, run policies, SEO, digest, kill switch). It's clearly distinguishable from the read sibling get_team_settings, though it never names that sibling explicitly.

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?

Conveys that this is a partial-update operation ('All fields are optional — only provided fields are changed'), which implies how to call it, but gives no explicit when-to-use/when-not guidance or pointers to get_team_settings for verification, nor any prerequisite (e.g. admin permission).

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

All validoria-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?