Create estate guest visit invites and read your Clannit notifications (including past invite codes…
Scored across 1 tool
There is only one tool, so there is no risk of misselection, but the name and description ('Clannit MCP') convey nothing about what operation it performs. An agent cannot predict its behavior or inputs from the surface.
A single name, 'bgpt_Clannit', mixes a cryptic prefix with a PascalCase proper noun and no verb, so there is no verb_noun convention to speak of. With only one tool, consistency cannot be established, and the name itself is uninformative.
One opaque tool for a server branded as a full MCP platform ('Clannit MCP by Nova') is an extreme mismatch. There is no way to express distinct operations or resources through a single catch-all entry point.
The domain cannot even be inferred from the tool name, and there are no create/read/update/delete or lifecycle operations exposed. Whatever Clannit does, the surface provides no discoverable coverage of it.
🛠️ Clannit MCP
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
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 and it delivers none: no indication of read vs write, side effects, reversibility, auth requirements, or rate limits. The emoji and name convey no behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The text is extremely short, but this is under-specification rather than conciseness: there is no front-loaded statement of purpose, and the sole content is decorative emoji plus a restated name.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Even for a parameterless tool with no output schema, the definition supplies no information about what the tool does or returns, so an agent has no basis for selection or invocation. The absence of annotations and siblings removes every other source of context, leaving the description entirely inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema defines zero parameters, so per the baseline rule for parameterless tools a 4 applies; the description is not required to explain parameters that do not exist. The only shortfall is that no parameter discussion is possible, but nothing is undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is the string "🛠️ Clannit MCP", which restates the tool name with a hammer emoji and adds no verb, resource, or scope. An agent cannot determine what operation this performs or what domain it operates on.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no exclusion criteria, and no alternatives named. With no siblings listed and no text in the description, there is nothing to route an agent toward or away from this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bgpt_Clannitcreate_guest_invitefetch_external_resource_filefetch_forum_announcementsfetch_forum_profile_photofetch_guest_invite_advertisementsfetch_notificationsfetch_resourcefetch_user_profile_picturefetch_user_schoollist_forum_postslogin_and_register_push_notificationsbgpt_Clannitcreate_guest_invitefetch_external_resource_filefetch_forum_announcementsfetch_forum_profile_photofetch_guest_invite_advertisementsfetch_notificationsfetch_resourcefetch_user_profile_picturefetch_user_schoollist_forum_postslogin_and_register_push_notificationsbgpt_Clannitcreate_guest_invitefetch_external_resource_filefetch_forum_announcementsfetch_forum_profile_photofetch_guest_invite_advertisementsfetch_notificationsfetch_resourcefetch_user_profile_picturefetch_user_schoollist_forum_postslogin_and_register_push_notificationscreate_guest_invitefetch_external_resource_filefetch_forum_announcementsfetch_forum_profile_photofetch_guest_invite_advertisementsfetch_notificationsfetch_resourcefetch_user_profile_picturefetch_user_schoollist_forum_postslogin_and_register_push_notificationsRead contacts, listings, tenancies and tasks; create a person contact, note or reminder.
Buzz in deliveries and guests: apartment access codes, timed or recurring entry, and access history.
Your household's calendar, tasks, messages and apps. Read, update, or build new apps with AI.
Read Street.co.uk properties, applicants, viewings, tenancies, jobs; create enquiries, notes, tasks.
Add one secure layer between your agents and this server.