Skip to main content
Glama
ricCap

Sketch Engine MCP Server

by ricCap

get_word_sketch_diff

Compare two words by analyzing their collocations to reveal which collocations are more typical of each word. Useful for distinguishing between similar terms.

Instructions

Compare the behavior of two words/lemmas via their collocations. Returns scores indicating which collocation is more typical of which word, useful for observing differences between similar words.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lposNoPart of speech filter (e.g., 'n' for noun, 'v' for verb) (optional)
lemmaYesFirst lemma to compare
formatNoResponse formatjson
lemma2YesSecond lemma to compare
diff_byNoComparison mode: 'lemma' compares two lemmas (default), 'word form' compares word forms of same lemma, 'subcorpus' compares same lemma in different subcorpora (optional)
minfreqNoMinimum frequency threshold for collocations (optional)
corpnameYesName of the corpus
subcorp1NoFirst subcorpus name (requires diff_by='subcorpus') (optional)
subcorp2NoSecond subcorpus name (requires diff_by='subcorpus') (optional)
maxcommonNoMaximum number of common collocations to show (optional)
wordform1NoFirst word form to compare (requires diff_by='word form') (optional)
wordform2NoSecond word form to compare (requires diff_by='word form') (optional)
maxexclusiveNoMaximum number of exclusive collocations per word (optional)
separate_blocksNoSeparate collocations into blocks by grammatical relation (optional)
Behavior3/5

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

No annotations provided, so description carries full burden. It states it compares collocations and returns scores but does not disclose limitations, required permissions, rate limits, or response structure beyond scores.

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?

Single sentence is concise and front-loaded with purpose. No wasted words, though could benefit from slight elaboration on how scores work.

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?

Given the tool's complexity (14 parameters) and no output schema, the description is adequate but incomplete. It lacks details on response format, sorting, or edge cases, but schema covers parameters well.

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?

Schema coverage is 100%, so baseline is 3. The description adds minimal value beyond schema—just mentions 'collocations' and 'scores' but does not explain how scores are calculated or interpreted.

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?

Description clearly states it compares two words/lemmas via collocations and returns scores indicating which collocation is more typical. It explicitly mentions usefulness for observing differences between similar words, distinguishing it from siblings like get_word_sketch (single word) and get_collocations (no comparison).

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?

Description implies usage for comparing similar words but does not explicitly state when to use this tool over alternatives like get_word_sketch or get_collocations. No guidance on when not to use or prerequisites.

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

Install Server

Other Tools

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/ricCap/sketch-engine-mcp-server'

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