Meseriasi MCP Server

create_project

Create a new project on meseriasi.ro as a homeowner. Notifies nearby tradespeople automatically. Requires the caller to supply a valid Supabase access token in the "access_token" argument.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Short descriptive title for the project (max 255 chars)
`budget`	No	Approximate budget in RON (optional)
`location`	Yes	City / address where the work is needed
`tradeType`	Yes	Category of trade required (e.g. "electrician", "instalator")
`description`	No	Detailed description of the work needed
`access_token`	Yes	Supabase JWT access token for the homeowner account

TDQS

A4.2/5.0

Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses key behaviors: automatic notification of nearby tradespeople and the requirement for a Supabase access token. It does not mention side effects, rate limits, or error conditions, but the disclosed behaviors are important.

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 sentences, short and front-loaded. It immediately states the purpose and then adds key behavioral and auth details without redundancy.

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?

Given the schema covers all parameters, no output schema, and no annotations, the description provides a high-level overview including automatic notification and auth requirement. It could elaborate on return values or failure modes, but it is sufficiently complete for its complexity.

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 the input schema already describes all parameters with individual descriptions. The description adds minor context (homeowner role, access token requirement) but does not significantly enhance understanding beyond the schema. Baseline 3 is appropriate.

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 verb 'Create', the resource 'project', and the context 'on meseriasi.ro as a homeowner'. It also mentions automatic notification of tradespeople, which distinguishes it from sibling tools like search_tradespeople or start_conversation.

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 indicates it is for homeowners and requires a valid access token. It implies usage when creating a project but does not explicitly state when not to use or list alternatives. However, the context is clear and the sibling tools are sufficiently different.

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

All Meseriasi MCP Server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Each tool targets a distinct action: project creation, profile retrieval, OTP request, tradesperson search, and conversation initiation. No two tools have overlapping purposes, ensuring clear agent selection.

Naming Consistency4/5

Tools generally follow verb_noun pattern (e.g., create_project, search_tradespeople). Minor inconsistency: 'tradesperson_profile' uses singular while 'tradespeople' uses plural, but overall pattern is consistent and readable.

Tool Count5/5

With 5 tools covering project creation, search, profiles, and chat, the set is well-scoped for a homeowner-tradesperson matching server. Each tool serves a clear role without redundancy.

Completeness3/5

Core workflow is covered (create project, search, start conversation), but notable gaps exist: no tools for updating/deleting projects, viewing bids, or managing conversations. Agents may face dead ends.

Resources

Need Help?