Skip to main content
Glama
deenesjakoruzh
MaryamSarfraz77

Dictionary Lookup MCP Server

by MaryamSarfraz77
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

Dictionary Lookup MCP Server

A minimal Model Context Protocol server built with the official Python SDK. It exposes one tool, define, which looks up the definition of an English word using the free dictionaryapi.dev API.

This project was built as a learning exercise to understand how MCP servers are structured, how they communicate with clients, and how to deploy one publicly.

What it does

  • Exposes a single tool: define(word: str) -> str

  • Given a word, returns its part of speech and definition

  • No API key or authentication required

Related MCP server: Hello World MCP FastAPI Endpoint

Requirements

  • Python 3.10+

  • uv (recommended) or pip

Setup (local)

# 1. Clone this repo
git clone <your-repo-url>
cd my-mcp-server

# 2. Install dependencies
uv sync

Running it locally

Option A — MCP Inspector (visual testing tool, easiest for beginners):

uv run mcp dev server.py

This opens a browser-based inspector where you can call the define tool directly and see the request/response without needing a full AI client.

Option B — Connect to Claude Desktop:

Add this to your Claude Desktop config file (claude_desktop_config.json):

{
  "mcpServers": {
    "dictionary-lookup": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/my-mcp-server",
        "run",
        "server.py"
      ]
    }
  }
}

Restart Claude Desktop, then ask something like: "Use the dictionary tool to define 'ephemeral'."

Usage example

Input: define("ephemeral") Output: ephemeral (adjective): lasting for a very short time.

Deployment

This server is published on Smithery: <link once deployed>

To deploy your own copy:

  1. Push this repo to GitHub.

  2. Ensure server.py supports the streamable-http transport for remote hosting.

  3. Host it (e.g. Render/Railway) or use Smithery's publish flow.

  4. On Smithery, choose "Publish via URL" and point it at your hosted server's endpoint.

Why this project

Built to learn the fundamentals of MCP: how a client discovers a server's tools, how a tool call is made and answered, and how a working server gets shared publicly through a marketplace like Smithery.

Available Tools

1 tool
defineA

Look up the definition of an English word and return it as text.

ParametersJSON Schema
NameRequiredDescriptionDefault
wordYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.4/5.0
Behavior4/5

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

There are no annotations, so the description carries the full behavioral burden. It conveys a read-only lookup behavior by saying 'Look up' and specifies the return type as 'text.' It does not cover edge cases like unknown words or multiple definitions, but these are not critical for a simple dictionary lookup tool.

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, front-loaded sentence that directly states the action, scope, and output. Every word earns its place and there is no unnecessary elaboration 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 single-parameter read-only lookup tool with an output schema, the description is substantially complete. It covers the input type ('English word'), the operation, and the return format ('text'). It does not mention failure behavior, but that is a minor gap given the tool's simplicity.

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?

The input schema only has a parameter titled 'Word' with zero description coverage. The description compensates by specifying that the word must be an English word, which adds meaningful semantic context beyond the schema. Though format and edge cases are not detailed, the parameter and its expected value are straightforward.

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 uses a specific verb ('Look up') and a clear resource ('the definition of an English word'), and it states the output form ('return it as text'). There are no sibling tools, so no differentiation is needed. This makes the tool's purpose immediately obvious.

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 when to use the tool: whenever an agent needs to retrieve the meaning of an English word. It also implicitly excludes non-English words. Because there are no sibling tools or alternatives, explicit when-not-to-use guidance is not necessary.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observeddefine
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is immediately clear and unambiguous.

Naming Consistency5/5

The single tool name 'define' is a clear imperative verb that matches its action. With only one tool, there are no mixed naming conventions or inconsistencies.

Tool Count3/5

One tool feels thin for a server labeled as a dictionary lookup service, though it does cover the core definition lookup need. It is borderline rather than extreme.

Completeness4/5

The core lookup functionality is covered well, but a dictionary server might reasonably include related operations like synonyms, usage examples, or pronunciation. These are minor gaps rather than fatal omissions.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Hello World MCP FastAPI

    bankszach
    F
    license
    Not graded
    quality
    D
    maintenance
    A minimal Model Context Protocol server built with FastAPI that provides a basic "Hello World" resource and tool. Serves as a starting point for building and validating MCP client integrations with richer resources and tools.
    -

  • mcp-server-http-streamable

    douglasqsantos
    A
    license
    Not graded
    quality
    D
    maintenance
    A minimal Model Context Protocol server that facilitates network-based client connections using Streamable HTTP transport. It provides a greeting tool and is optimized for consistent deployment across local environments, Docker, and Kubernetes.
    MIT

  • yifanli-mcp-add-demo

    tryp0xy1us
    F
    license
    B
    quality
    Not graded
    maintenance
    A minimal Model Context Protocol server that provides a simple tool for adding two integers. It serves as a demonstration of the official Python MCP SDK and is designed for local execution via stdio.
    1
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MaryamSarfraz77/dictionary-lookup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server