PyScrappy

by mldsveda

Overview Schema Source Related Servers Discussions Admin

Python

Define Word

define_word

Look up an English word to retrieve its definitions, parts of speech, and example sentences from an online dictionary.

Instructions

Look up an English word and return its dictionary entry: definitions, part(s) of speech, and example sentences.

Fetches from an online dictionary data source, so a network connection is required. Read-only with no side effects. If the word is not found (misspelled or not in the dictionary), returns an empty result or a not-found response rather than raising.

Returns a structured entry for the word, typically containing the word itself, one or more part-of-speech groupings, and for each a list of definitions with optional example sentences.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`word`	Yes	The English word to define, as a string. Example: "serendipity". No default (required). Single words only; not phrases or non-English terms.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`count`	No
`errors`	No
`scraper`	No
`source_urls`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 31, 2026

changedInput schema / properties / word / description

Previous value: -"The word to define."New value: +"The English word to define, as a string. Example: \"serendipity\". No default (required). Single words only; not phrases or non-English terms."

Changed16 schema fields changedv1.3.3Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / word / description
```
Added value: +"The word to define."
```
removedInput schema / properties / word / title
```
Removed value: -"Word"
```
removedInput schema / title
```
Removed value: -"define_wordArguments"
```

removedOutput schema / $defs

Removed value: -{
-  "ToolError": {
-    "description": "A non-fatal problem encountered while scraping.",
-    "properties": {
-      "message": {
-        "title": "Message",
-        "type": "string"
-      },
-      "url": {
-        "title": "Url",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "message"
-    ],
-    "title": "ToolError",
-    "type": "object"
-  }
-}

removedOutput schema / properties / count / title
```
Removed value: -"Count"
```
removedOutput schema / properties / data / title
```
Removed value: -"Data"
```
removedOutput schema / properties / errors / items / $ref
```
Removed value: -"#/$defs/ToolError"
```

addedOutput schema / properties / errors / items / description

Added value: +"A non-fatal problem encountered while scraping."

addedOutput schema / properties / errors / items / properties

Added value: +{
+  "message": {
+    "type": "string"
+  },
+  "url": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / errors / items / required
```
Added value: +[
+  "url",
+  "message"
+]
```
addedOutput schema / properties / errors / items / type
```
Added value: +"object"
```
removedOutput schema / properties / errors / title
```
Removed value: -"Errors"
```
removedOutput schema / properties / scraper / title
```
Removed value: -"Scraper"
```
removedOutput schema / properties / source_urls / title
```
Removed value: -"Source Urls"
```
removedOutput schema / title
```
Removed value: -"ScrapeToolResult"
```

AddedJul 26, 2026

TDQS

A4/5.0

Behavior4/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 of behavioral disclosure. It explicitly notes that the tool is read-only with no side effects, requires a network connection, and handles not-found cases by returning an empty or not-found response instead of raising an error. It also describes the structure of the return value. This is substantial coverage for a simple lookup tool, though it could mention rate limits or authentication if applicable.

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 two short paragraphs with no fluff. The purpose is front-loaded in the first sentence, and the second paragraph adds essential behavioral details (network, error handling, return structure). Every sentence earns its place, and the length is appropriate for the tool's complexity.

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?

The tool is simple with one parameter and a structured output schema. The description covers the purpose, behavioral notes, and a summary of the return value. Given that an output schema exists, the description does not need to detail every field. It is complete enough for an agent to understand what the tool does and how to invoke it correctly.

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

Parameters3/5

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

The input schema has 100% coverage and already fully describes the 'word' parameter, including its type, example, required status, and constraints (single words only). The tool description does not add any additional meaning beyond what the schema already provides, so it meets the baseline of 3 for a high-coverage schema. No further elaboration is needed.

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 (look up an English word) and the resource (dictionary entry), listing specific content: definitions, parts of speech, and example sentences. It is distinct from the sibling tools, which are all web scraping or search tools, so there is no ambiguity about what this tool does.

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?

The description does not explicitly state when to use this tool versus alternatives, though the sibling list makes it obvious it is for dictionary lookups. It does provide a constraint in the schema parameter (single words only, not phrases or non-English terms), but there is no explicit routing guidance such as 'use this when you need a definition rather than scraping a page.' The intended use is implied rather than stated.

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