Skip to main content
Glama
Sign In
dolphin-anty-mcp

dolphin-anty-mcp

by someorgyouwontcareabout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a browser profile

get_profile
Read-only

Retrieve a browser profile by ID and access its full fingerprint to inspect or configure anti-detect settings.

Instructions

Fetch one browser profile by id, including its full fingerprint.

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": {
      "id": "<id>"
    },
    "name": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The readOnlyHint annotation already communicates the safe read-only nature, so no need to repeat. The description adds value by disclosing that the result includes the full fingerprint, which is non-obvious and useful behavioral/return information.

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?

One sentence, eleven words, front-loaded with the verb and resource. Every word earns its place; no filler or repetition.

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 simple single-fetch tool, the description covers the key points: what is fetched (profile by id) and a notable detail (full fingerprint). Given the annotations cover safety and there are no nested objects, this is sufficiently complete, though it could mention error cases or absence behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate. It only says 'by id', which essentially just repeats the parameter name 'id' without explaining the id's origin, format, or relationship to the profile. The schema states it's an integer, but the description adds little meaning beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (fetch), the resource (one browser profile by id), and specifies that it includes the full fingerprint. This distinguishes it from sibling tools like list_profiles (which fetch many) and get_fingerprint (which fetches only a fingerprint).

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?

The description clearly implies the use case: when you need a single profile identified by its id. It does not explicitly mention alternatives or when-not-to-use, but the context is unambiguous.

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