Skip to main content
Glama
Sign In

Testsy

by dev.testsy
OverviewDiscussionsAdmin

Set the browsing country

set_browse_from

Choose the country our browsers visit your sites from (web tests), or automatic: the site's own country.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "country": "<country>"
    },
    "name": "set_browse_from"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesTwo-letter country code (see get_network), or "auto"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds real behavioral meaning by explaining that the setting governs which country browsers originate from and what 'auto' resolves to. It omits scope (workspace-wide vs per-project) and whether the change persists across runs, which matters for a mutation.

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?

One compact sentence with the effect front-loaded and the qualifier placed where it disambiguates. Nothing is padded, though the '(web tests)' parenthetical slightly interrupts the flow and could be restructured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter setter with a fully described schema and clear annotations, most of what an agent needs is present. The remaining gap is scope — whether this applies to all browser tests in the workspace or only some — which is not covered by any structured field and is not answered here.

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 100% and the single parameter already documents the two-letter code and the literal "auto". The description goes beyond that by defining what "auto" actually means — the site's own country — which the schema does not state. That is genuine added semantics over a fully documented 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 and effect: choosing the country 'our browsers visit your sites from', plus the web-test scope. An agent can immediately tell this is an egress-location setting for browser traffic. It does not name a sibling it displaces, but the purpose itself is unambiguous.

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?

Usage is only implied: the '(web tests)' parenthetical tells the agent this applies to browser-based tests, and 'or automatic' hints at the alternative value. There is no explicit guidance on when to change this setting versus leaving it at 'auto', nor any mention of get_network as the companion for discovering valid codes.

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

All Testsy toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources