dolphin-anty-mcp

Update a homepage

update_homepage

Update a startup page entry by changing only the fields you specify, such as name, URL, main website, or team sharing.

Instructions

Change a startup page entry. Only the fields you pass are modified.

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": "update_homepage"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`data`	No
`mainWebsite`	No
`sharedToEntireTeam`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description adds the behavioral detail 'Only the fields you pass are modified', which is valuable for partial-update semantics. Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false), so the description complements rather than contradicts them. No mention of permissions or side effects, but the annotations lower the bar.

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?

The description is a single sentence of 10 words, conveying the core behavior without any redundancy. It is front-loaded and every word earns its place.

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?

The description covers the essential behavior (partial update) but is minimal. Given the lack of an output schema and low parameter explanation, an agent may need to infer what fields like 'data' or 'mainWebsite' represent. The field names and enum values provide some context, but the description does not fully compensate for the missing schema descriptions.

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?

Schema description coverage is 0%, so the description must compensate by explaining parameter meaning. It only says 'fields you pass are modified', which clarifies that parameters are optional fields for partial updates, but it does not explain the semantics of 'data', 'mainWebsite', or 'sharedToEntireTeam'. The parameter names are moderately self-explanatory, but the description does not help an agent understand their structure or purpose.

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 'Change a startup page entry' clearly identifies the action (change) and the resource (startup page entry), distinguishing it from sibling tools like create_homepages, delete_homepages, and list_homepages. The verb is specific and the resource is well-defined in context.

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 implied by the verb 'change' and the tool name 'update_homepage', suggesting it is for modifying existing homepages. However, there is no explicit guidance on when to use this tool versus alternatives such as create_homepages or delete_homepages, nor any exclusions or conditions.

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

Deploy Server