Dengdeng Chinese Dictionary

Get dictionary widget code

get_embed_code

Read-onlyIdempotent

Get the HTML code to put a free Dengdeng dictionary widget on a website, for example a teacher's class page or a blog. Widgets: word_card (a word with pinyin, meanings, a sound button and a link to the word's cartoon when it has one), word_of_the_day (a new common word every day) and search_box (a dictionary search form). The code is an iframe plus a plain credit link; tell the user to paste both into an HTML or embed block. Returns the code, the frame URL and size, and the widgets page with instructions for WordPress and Google Sites.

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": {
      "widget": "<widget>"
    },
    "name": "get_embed_code"
  }
}

Input Schema

Name	Required	Description	Default
`word`	No	The Chinese word for word_card, for example 谢谢. Not used by word_of_the_day and search_box.
`widget`	Yes	Which widget to embed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world). Beyond that, the description discloses the composition of the result (an iframe plus a plain credit link), the return payload (code, frame URL and size, widgets page), and the WordPress/Google Sites instructions — meaningful operational context not in the annotations.

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, then the widget options, then the paste instruction and return shape. Four sentences with no filler; the parenthetical widget descriptions are long but carry selection-relevant information.

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?

For a two-parameter read-only tool with no output schema, the description covers purpose, parameter meaning, return contents, and the user-facing next step — nothing an agent needs in order to call it correctly 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?

Schema coverage is 100%, so a baseline of 3 applies, but the description adds real meaning to the widget enum by describing what each widget renders and clarifies the embedding scenario the parameters serve.

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?

States a precise verb and resource — retrieving HTML embed code for a dictionary widget — and enumerates the three widget variants with a one-line characterization of each, which distinguishes it clearly from the sibling lookup tools.

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?

Gives concrete usage contexts (a teacher's class page, a blog) and a follow-through instruction to have the user paste both the iframe and the credit link into an HTML or embed block. It does not explicitly exclude alternatives, but the embedding use case is unambiguous.

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

All Dengdeng Chinese Dictionary 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?