> For the complete documentation index, see [llms.txt](https://docs.pentafloat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentafloat.com/documentation/converters/custom-parameter-types.md).

# Custom parameter types

To demonstrate how a custom type can be supported, we are going to create a converter for an arbitrary class.

```csharp
public class Person
{
    public readonly string name;
    public readonly int age;

    public Person(string name, int age)
    {
        this.name = name;
        this.age = age;
    }
}
```

## Converter methods

The way converters work, is by creating a method that takes in a `string` and return an actual value. Converter methods must return a non-primitive type, and they must only take **1** parameter of type `ArgumentReader`.

To mark a method as a converter method, simply place a `[Converter]` attribute on it.

```cs
[Converter]
public static Person PersonTypeConverter(ArgumentReader reader)
{
    
}
```

{% hint style="info" %}
**Note**

The method doesn't have to be located within the type we're attempting to convert. These methods can be stored anywhere you prefer
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentafloat.com/documentation/converters/custom-parameter-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.